|
+
3.1 The ‘flow-into’ property
|
|
content-node-layers-001 |
= |
Ahem |
flowing content with opacity < 1 in region
- Test checks that content with opacity < 1 is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing.
|
|
content-node-layers-002 |
= |
Ahem |
flowing content with scrollbars in region
- Test checks that content with scrollbars is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing.
|
|
content-node-layers-003 |
= |
Ahem |
flowing content that's relatively positioned and get fragmented
- Test checks that content that's relatively positioned gets properly fragmented between regions.
|
|
content-node-layers-004 |
= |
Ahem |
flowing content with opacity < 1 and opacity = 1 in region
- Test checks that content nodes with mixed opacity < 1 and opacity = 1 is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing.
|
|
content-node-layers-005 |
= |
Ahem |
flowing content with position: absolute and clip
- Test checks that absolutely positioned content that has the clip property applied is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing or the clipping shapes.
|
|
extract-ordered-list-direction-and-writing-modes |
= |
|
flow-into on list items that use different text directions or writing modes
- The flow-into property can be applied to elements that have different text directions and writing modes. This tests that the rendering for lists that use different text directions/writing modes are not affected when they are extracted in a named flow and rendered in a region.
|
|
flow-into-001 |
= |
|
flow-into behavior
- Elements placed into a named flow follow document order. Children of flow elements can be placed in a different flow. Nested flow elements in the same flow become siblings. Flow-into is not inherited.
|
|
flow-into-invalid-names-001 |
= |
|
invalid flow-into idents
- If flow-into is set to an invalid ident, no flow is created. The flow content will stay in its green wrapper. Invalid idents with flow-from do not create a region.
|
|
javascript-stacking-context-001 |
|
Ahem |
document.elementFromPoint() for overlapping, positioned regions with non-auto z-index
- Test checks that document.elementFromPoint() returns the correct region when multiple regions are absolutely positioned, overlap and have non-auto z-index.
|
|
javascript-stacking-context-002 |
|
Ahem |
JavaScript event handlers on overlapping, positioned regions with non-auto z-index
- Test checks that JavaScript event handlers set on regions trigger when multiple regions are absolutely positioned, overlap and have non-auto z-index.
|
|
regions-dialog-001 |
= |
DOM/JS |
flowing content in dialog
- Test checks that content is correctly flowed into dialog elements.
|
|
regions-dialog-002 |
= |
DOM/JS |
flowing dialog elements in region
- Test checks that dialog elements are correctly flowed into a region.
|
|
regions-layers-001 |
= |
Ahem |
flowing content in regions that have a non-auto z-index
- Test checks that making the region create a stacking context by setting a non-auto z-index does not affect rendering of the content flowed in the region.
|
|
regions-layers-002 |
= |
Ahem |
flowing content in regions that have opacity < 1 with the content also having opacity < 1
- Test checks that region's opacity is properly composited with content opacity.
|
|
regions-layers-003 |
= |
Ahem |
flowing content in regions that are absolutely positioned and have visual overflow
- Test checks that region's visual overflow is displayed when region is absolutely positioned and has visual overflow.
|
|
regions-modal-dialog-001 |
= |
DOM/JS |
flowing content in a modal dialog
- Test checks that content is correctly flowed into modal dialog elements.
|
|
regions-modal-dialog-002 |
= |
DOM/JS |
flowing modal dialog elements in region
- Test checks that modal dialog elements are correctly flowed into a region.
|
|
regions-mouse-events-001 |
|
DOM/JSInteract |
CSS Regions: onclick events inside region and outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse onclick events inside and outside a named flow should function correctly.
|
|
regions-mouse-events-002 |
|
DOM/JSInteract |
CSS Regions: onmousedown events inside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmousedown events inside a named flow should function correctly.
|
|
regions-mouse-events-003 |
|
DOM/JSInteract |
CSS Regions: onmousedown events outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmousedown events outside a named flow should function correctly.
|
|
regions-mouse-events-004 |
|
DOM/JSInteract |
CSS Regions: onmouseup events inside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseup events inside a named flow should function correctly.
|
|
regions-mouse-events-005 |
|
DOM/JSInteract |
CSS Regions: onmouseup events outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseup events outside a named flow should function correctly.
|
|
regions-mouse-events-006 |
|
DOM/JSInteract |
CSS Regions: ondblclick events inside region and outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse ondblclick events inside and outside a named flow should function correctly.
|
|
regions-mouse-events-007 |
|
DOM/JSInteract |
CSS Regions: onmousemove events inside region and outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmousemove events inside and outside a named flow should function correctly.
|
|
regions-mouse-events-008 |
|
DOM/JSInteract |
CSS Regions: onmouseover and onmouseout events inside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseover and onmouseout events inside a named flow should function correctly.
|
|
regions-mouse-events-009 |
|
DOM/JSInteract |
CSS Regions: onmouseover and onmouseout events outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseover and onmouseout events outside a named flow should function correctly.
|
|
regions-selection-001 |
|
DOM/JSInteract |
Selection begins at the top of the region and ends at the bottom of the region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse the movement.
|
|
regions-selection-002 |
|
DOM/JSInteract |
Selection begins at the bottom of the region and ends at the top of the region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-003 |
|
DOM/JSInteract |
Selection begins at the top of the region and ends in the middle of region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-004 |
|
DOM/JSInteract |
Selection begins at the bottom of the region and ends in the middle of region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-005 |
|
DOM/JSInteract |
CSS Regions: Selection begins in the middle of the region and ends in the middle of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-006 |
|
DOM/JSInteract |
Selection begins in the middle of the region and ends in the middle of the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-007 |
|
DOM/JSInteract |
Selection begins at the top of the region and ends outside the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-008 |
|
DOM/JSInteract |
Selection begins at the bottom of the region and ends outside the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-009 |
|
DOM/JSInteract |
Selection begins in the middle of the region and ends outside the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-010 |
|
DOM/JSInteract |
Selection begins in the middle of the region and ends outside the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-011 |
|
DOM/JSInteract |
Selection begins outside of the region and ends at the bottom of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-012 |
|
DOM/JSInteract |
Selection begins outside of the region and ends at the top the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-013 |
|
DOM/JSInteract |
Selection begins outside of the region and ends in the middle of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-014 |
|
DOM/JSInteract |
Selection begins outside of the region and ends in the middle of the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-015 |
|
DOM/JSInteract |
Selection begins and ends outside of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-016 |
|
DOM/JSInteract |
Selection begins and ends outside of the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-017 |
|
DOM/JSInteract |
Selection is downward, begins and ends inside a region containing one other element - div
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-018 |
|
DOM/JSInteract |
Selection is downward, begins and ends inside a region containing one other element - img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-019 |
|
DOM/JSInteract |
Selection is upward, begins and ends inside a region containing one other element - div
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-020 |
|
DOM/JSInteract |
Selection is upward, begins and ends inside a region containing one other element - img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-021 |
|
DOM/JSInteract |
Selection is downward, begins and ends inside a region containing two other elements - div + img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-022 |
|
DOM/JSInteract |
CSS Regions: Selection is upward, begins and ends inside a region containing two other elements - div + img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-023 |
|
DOM/JSInteract |
Selection is downward, begins inside a region and ends outside of it - both the region and the content after it have child elements
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-024 |
|
DOM/JSInteract |
CSS Regions: Selection is upward, begins inside and ends outside a region - both the region and the before after it have child elements
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mousemovement, including nested elements.
|
|
regions-selection-025 |
|
DOM/JSInteract |
DOM order is different than the linear selection
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection should capture content in DOM order as it would without a named flow.
|
|
regions-stacking-context-001 |
= |
Ahem |
regions as part of the root stacking context
- Test checks that regions respect stacking rules when part of the root stacking context.
|
|
regions-stacking-context-002 |
= |
Ahem |
regions as part of a non-root stacking context
- Test checks that regions respect stacking rules when part of a non-root stacking context.
|
|
regions-stacking-context-004 |
= |
Ahem |
regions create stacking contexts
- Test checks that regions create stacking contexts for content flowed into them.
|
|
regions-stacking-context-005 |
= |
Ahem |
regions changing stacking order when as part of a stacking context
- Test checks that regions stacking rules take precedence over content stacking rules.
|
|
variable-width-001 |
= |
|
Variable-width Regions
- The second region should lay out two of the content boxes.
|
|
+
3.2 The ‘flow-from’ property
|
|
content-node-layers-001 |
= |
Ahem |
flowing content with opacity < 1 in region
- Test checks that content with opacity < 1 is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing.
|
|
content-node-layers-002 |
= |
Ahem |
flowing content with scrollbars in region
- Test checks that content with scrollbars is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing.
|
|
content-node-layers-003 |
= |
Ahem |
flowing content that's relatively positioned and get fragmented
- Test checks that content that's relatively positioned gets properly fragmented between regions.
|
|
content-node-layers-004 |
= |
Ahem |
flowing content with opacity < 1 and opacity = 1 in region
- Test checks that content nodes with mixed opacity < 1 and opacity = 1 is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing.
|
|
content-node-layers-005 |
= |
Ahem |
flowing content with position: absolute and clip
- Test checks that absolutely positioned content that has the clip property applied is correctly flowed into regions. This might fail on implementations that use layers for compositing but don't properly handle content flowing or the clipping shapes.
|
|
flow-from-001 |
= |
|
Region chain ordering
- Regions are ordered in a region chain according to their document order.
|
|
flow-from-content-property-001 |
= |
Bitmaps |
flow-from and content interaction.
- If the ‘content’ property is set to a url, none or inhibit on a region, that declaration has no effect.
|
|
flow-into-bfc-001 |
= |
|
Regions establish a new block formatting context
- A region set next to a float will clear the float in a new block formatting context.
|
|
flow-into-region-children-001 |
= |
|
Region children are formatted if directed to a flow
- The two regions in this test will swap their children.
|
|
javascript-stacking-context-001 |
|
Ahem |
document.elementFromPoint() for overlapping, positioned regions with non-auto z-index
- Test checks that document.elementFromPoint() returns the correct region when multiple regions are absolutely positioned, overlap and have non-auto z-index.
|
|
javascript-stacking-context-002 |
|
Ahem |
JavaScript event handlers on overlapping, positioned regions with non-auto z-index
- Test checks that JavaScript event handlers set on regions trigger when multiple regions are absolutely positioned, overlap and have non-auto z-index.
|
|
region-stacking-context-001 |
= |
|
Regions create new stacking context
- The z-index set on region content does not affect how they are stacked with siblings of the region.
|
|
regions-dialog-001 |
= |
DOM/JS |
flowing content in dialog
- Test checks that content is correctly flowed into dialog elements.
|
|
regions-dialog-002 |
= |
DOM/JS |
flowing dialog elements in region
- Test checks that dialog elements are correctly flowed into a region.
|
|
regions-layers-001 |
= |
Ahem |
flowing content in regions that have a non-auto z-index
- Test checks that making the region create a stacking context by setting a non-auto z-index does not affect rendering of the content flowed in the region.
|
|
regions-layers-002 |
= |
Ahem |
flowing content in regions that have opacity < 1 with the content also having opacity < 1
- Test checks that region's opacity is properly composited with content opacity.
|
|
regions-layers-003 |
= |
Ahem |
flowing content in regions that are absolutely positioned and have visual overflow
- Test checks that region's visual overflow is displayed when region is absolutely positioned and has visual overflow.
|
|
regions-modal-dialog-001 |
= |
DOM/JS |
flowing content in a modal dialog
- Test checks that content is correctly flowed into modal dialog elements.
|
|
regions-modal-dialog-002 |
= |
DOM/JS |
flowing modal dialog elements in region
- Test checks that modal dialog elements are correctly flowed into a region.
|
|
regions-mouse-events-001 |
|
DOM/JSInteract |
CSS Regions: onclick events inside region and outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse onclick events inside and outside a named flow should function correctly.
|
|
regions-mouse-events-002 |
|
DOM/JSInteract |
CSS Regions: onmousedown events inside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmousedown events inside a named flow should function correctly.
|
|
regions-mouse-events-003 |
|
DOM/JSInteract |
CSS Regions: onmousedown events outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmousedown events outside a named flow should function correctly.
|
|
regions-mouse-events-004 |
|
DOM/JSInteract |
CSS Regions: onmouseup events inside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseup events inside a named flow should function correctly.
|
|
regions-mouse-events-005 |
|
DOM/JSInteract |
CSS Regions: onmouseup events outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseup events outside a named flow should function correctly.
|
|
regions-mouse-events-006 |
|
DOM/JSInteract |
CSS Regions: ondblclick events inside region and outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse ondblclick events inside and outside a named flow should function correctly.
|
|
regions-mouse-events-007 |
|
DOM/JSInteract |
CSS Regions: onmousemove events inside region and outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmousemove events inside and outside a named flow should function correctly.
|
|
regions-mouse-events-008 |
|
DOM/JSInteract |
CSS Regions: onmouseover and onmouseout events inside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseover and onmouseout events inside a named flow should function correctly.
|
|
regions-mouse-events-009 |
|
DOM/JSInteract |
CSS Regions: onmouseover and onmouseout events outside region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, onmouseover and onmouseout events outside a named flow should function correctly.
|
|
regions-selection-001 |
|
DOM/JSInteract |
Selection begins at the top of the region and ends at the bottom of the region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse the movement.
|
|
regions-selection-002 |
|
DOM/JSInteract |
Selection begins at the bottom of the region and ends at the top of the region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-003 |
|
DOM/JSInteract |
Selection begins at the top of the region and ends in the middle of region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-004 |
|
DOM/JSInteract |
Selection begins at the bottom of the region and ends in the middle of region
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-005 |
|
DOM/JSInteract |
CSS Regions: Selection begins in the middle of the region and ends in the middle of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-006 |
|
DOM/JSInteract |
Selection begins in the middle of the region and ends in the middle of the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse.
|
|
regions-selection-007 |
|
DOM/JSInteract |
Selection begins at the top of the region and ends outside the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-008 |
|
DOM/JSInteract |
Selection begins at the bottom of the region and ends outside the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-009 |
|
DOM/JSInteract |
Selection begins in the middle of the region and ends outside the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-010 |
|
DOM/JSInteract |
Selection begins in the middle of the region and ends outside the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-011 |
|
DOM/JSInteract |
Selection begins outside of the region and ends at the bottom of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-012 |
|
DOM/JSInteract |
Selection begins outside of the region and ends at the top the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-013 |
|
DOM/JSInteract |
Selection begins outside of the region and ends in the middle of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-014 |
|
DOM/JSInteract |
Selection begins outside of the region and ends in the middle of the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-015 |
|
DOM/JSInteract |
Selection begins and ends outside of the region moving downward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-016 |
|
DOM/JSInteract |
Selection begins and ends outside of the region moving upward
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse.
|
|
regions-selection-017 |
|
DOM/JSInteract |
Selection is downward, begins and ends inside a region containing one other element - div
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-018 |
|
DOM/JSInteract |
Selection is downward, begins and ends inside a region containing one other element - img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-019 |
|
DOM/JSInteract |
Selection is upward, begins and ends inside a region containing one other element - div
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-020 |
|
DOM/JSInteract |
Selection is upward, begins and ends inside a region containing one other element - img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-021 |
|
DOM/JSInteract |
Selection is downward, begins and ends inside a region containing two other elements - div + img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-022 |
|
DOM/JSInteract |
CSS Regions: Selection is upward, begins and ends inside a region containing two other elements - div + img
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection within a region should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-023 |
|
DOM/JSInteract |
Selection is downward, begins inside a region and ends outside of it - both the region and the content after it have child elements
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mouse, including nested elements.
|
|
regions-selection-024 |
|
DOM/JSInteract |
CSS Regions: Selection is upward, begins inside and ends outside a region - both the region and the before after it have child elements
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection inside and outside of a named flow should contain all of the content dragged over by the mousemovement, including nested elements.
|
|
regions-selection-025 |
|
DOM/JSInteract |
DOM order is different than the linear selection
- CSS regions module does not alter the normal processing of events in the document tree. Therefore, mouse selection should capture content in DOM order as it would without a named flow.
|
|
regions-stacking-context-001 |
= |
Ahem |
regions as part of the root stacking context
- Test checks that regions respect stacking rules when part of the root stacking context.
|
|
regions-stacking-context-002 |
= |
Ahem |
regions as part of a non-root stacking context
- Test checks that regions respect stacking rules when part of a non-root stacking context.
|
|
regions-stacking-context-004 |
= |
Ahem |
regions create stacking contexts
- Test checks that regions create stacking contexts for content flowed into them.
|
|
regions-stacking-context-005 |
= |
Ahem |
regions changing stacking order when as part of a stacking context
- Test checks that regions stacking rules take precedence over content stacking rules.
|


John Smith
Spanish River School
test
John Smith
Spanish River School
test
John Smith
Spanish River School
test


File Operators¶
-
bpy.ops.file.
autopack_toggle
()¶ Automatically pack all external files into the .blend file
-
bpy.ops.file.
bookmark_add
()¶ Add a bookmark for the selected/active directory
-
bpy.ops.file.
bookmark_cleanup
()¶ Delete all invalid bookmarks
-
bpy.ops.file.
bookmark_delete
(index=-1)¶ Delete selected bookmark
Parameters: index (int in [-1, 20000], (optional)) – Index
-
bpy.ops.file.
bookmark_move
(direction='TOP')¶ Move the active bookmark up/down in the list
Parameters: direction (enum in ['TOP', 'UP', 'DOWN', 'BOTTOM'], (optional)) – Direction, Direction to move the active bookmark towards
TOP
Top, Top of the list.UP
Up.DOWN
Down.BOTTOM
Bottom, Bottom of the list.
-
bpy.ops.file.
cancel
()¶ Cancel loading of selected file
-
bpy.ops.file.
delete
()¶ Move selected files to the trash or recycle bin
-
bpy.ops.file.
directory_new
(directory="", open=False, confirm=True)¶ Create a new directory
Parameters: - directory (string, (optional, never None)) – Directory, Name of new directory
- open (boolean, (optional)) – Open, Open new directory
- confirm (boolean, (optional)) – Confirm, Prompt for confirmation
-
bpy.ops.file.
execute
(need_active=False)¶ Execute selected file
Parameters: need_active (boolean, (optional)) – Need Active, Only execute if there’s an active selected file in the file list
-
bpy.ops.file.
filenum
(increment=1)¶ Increment number in filename
Parameters: increment (int in [-100, 100], (optional)) – Increment
-
bpy.ops.file.
filepath_drop
(filepath="Path")¶ Undocumented contribute <https://developer.blender.org/T51061>
-
bpy.ops.file.
find_missing_files
(find_all=False, directory="", hide_props_region=True, filter_blender=False, filter_backup=False, filter_image=False, filter_movie=False, filter_python=False, filter_font=False, filter_sound=False, filter_text=False, filter_archive=False, filter_btx=False, filter_collada=False, filter_alembic=False, filter_usd=False, filter_folder=False, filter_blenlib=False, filemode=9, display_type='DEFAULT', sort_method='FILE_SORT_ALPHA')¶ Try to find missing external files
Parameters: - find_all (boolean, (optional)) – Find All, Find all files in the search path (not just missing)
- directory (string, (optional, never None)) – Directory, Directory of the file
- hide_props_region (boolean, (optional)) – Hide Operator Properties, Collapse the region displaying the operator settings
- filter_blender (boolean, (optional)) – Filter .blend files
- filter_backup (boolean, (optional)) – Filter .blend files
- filter_image (boolean, (optional)) – Filter image files
- filter_movie (boolean, (optional)) – Filter movie files
- filter_python (boolean, (optional)) – Filter python files
- filter_font (boolean, (optional)) – Filter font files
- filter_sound (boolean, (optional)) – Filter sound files
- filter_text (boolean, (optional)) – Filter text files
- filter_archive (boolean, (optional)) – Filter archive files
- filter_btx (boolean, (optional)) – Filter btx files
- filter_collada (boolean, (optional)) – Filter COLLADA files
- filter_alembic (boolean, (optional)) – Filter Alembic files
- filter_usd (boolean, (optional)) – Filter USD files
- filter_folder (boolean, (optional)) – Filter folders
- filter_blenlib (boolean, (optional)) – Filter Blender IDs
- filemode (int in [1, 9], (optional)) – File Browser Mode, The setting for the file browser mode to load a .blend file, a library or a special file
- display_type (enum in ['DEFAULT', 'LIST_VERTICAL', 'LIST_HORIZONTAL', 'THUMBNAIL'], (optional)) –
Display Type
DEFAULT
Default, Automatically determine display type for files.LIST_VERTICAL
Short List, Display files as short list.LIST_HORIZONTAL
Long List, Display files as a detailed list.THUMBNAIL
Thumbnails, Display files as thumbnails.
- sort_method (enum in ['FILE_SORT_ALPHA', 'FILE_SORT_EXTENSION', 'FILE_SORT_TIME', 'FILE_SORT_SIZE'], (optional)) –
File sorting mode
FILE_SORT_ALPHA
Name, Sort the file list alphabetically.FILE_SORT_EXTENSION
Extension, Sort the file list by extension/type.FILE_SORT_TIME
Modified Date, Sort files by modification time.FILE_SORT_SIZE
Size, Sort files by size.
-
bpy.ops.file.
hidedot
()¶ Toggle hide hidden dot files
-
bpy.ops.file.
highlight
()¶ Highlight selected file(s)
-
bpy.ops.file.
make_paths_absolute
()¶ Make all paths to external files absolute
-
bpy.ops.file.
make_paths_relative
()¶ Make all paths to external files relative to current .blend
-
bpy.ops.file.
next
()¶ Move to next folder
-
bpy.ops.file.
pack_all
()¶ Pack all used external files into the .blend
-
bpy.ops.file.
pack_libraries
()¶ Pack all used Blender library files into the current .blend
-
bpy.ops.file.
parent
()¶ Move to parent directory
-
bpy.ops.file.
previous
()¶ Move to previous folder
-
bpy.ops.file.
refresh
()¶ Refresh the file list
-
bpy.ops.file.
rename
()¶ Rename file or file directory
-
bpy.ops.file.
report_missing_files
()¶ Report all missing external files
-
bpy.ops.file.
reset_recent
()¶ Reset Recent files
-
bpy.ops.file.
select
(extend=False, fill=False, open=True, deselect_all=False)¶ Handle mouse clicks to select and activate items
Parameters: - extend (boolean, (optional)) – Extend, Extend selection instead of deselecting everything first
- fill (boolean, (optional)) – Fill, Select everything beginning with the last selection
- open (boolean, (optional)) – Open, Open a directory when selecting it
- deselect_all (boolean, (optional)) – Deselect On Nothing, Deselect all when nothing under the cursor
-
bpy.ops.file.
select_all
(action='TOGGLE')¶ Select or deselect all files
Parameters: action (enum in ['TOGGLE', 'SELECT', 'DESELECT', 'INVERT'], (optional)) – Action, Selection action to execute
TOGGLE
Toggle, Toggle selection for all elements.SELECT
Select, Select all elements.DESELECT
Deselect, Deselect all elements.INVERT
Invert, Invert selection of all elements.
-
bpy.ops.file.
select_bookmark
(dir="")¶ Select a bookmarked directory
Parameters: dir (string, (optional, never None)) – Dir
-
bpy.ops.file.
select_box
(xmin=0, xmax=0, ymin=0, ymax=0, wait_for_input=True, mode='SET')¶ Activate/select the file(s) contained in the border
Parameters: - xmin (int in [-inf, inf], (optional)) – X Min
- xmax (int in [-inf, inf], (optional)) – X Max
- ymin (int in [-inf, inf], (optional)) – Y Min
- ymax (int in [-inf, inf], (optional)) – Y Max
- wait_for_input (boolean, (optional)) – Wait for Input
- mode (enum in ['SET', 'ADD', 'SUB'], (optional)) –
Mode
SET
Set, Set a new selection.ADD
Extend, Extend existing selection.SUB
Subtract, Subtract existing selection.
-
bpy.ops.file.
select_walk
(direction='UP', extend=False, fill=False)¶ Select/Deselect files by walking through them
Parameters: - direction (enum in ['UP', 'DOWN', 'LEFT', 'RIGHT'], (optional)) – Walk Direction, Select/Deselect file in this direction
- extend (boolean, (optional)) – Extend, Extend selection instead of deselecting everything first
- fill (boolean, (optional)) – Fill, Select everything beginning with the last selection
-
bpy.ops.file.
smoothscroll
()¶ Smooth scroll to make editable file visible
-
bpy.ops.file.
sort_column_ui_context
()¶ Change sorting to use column under cursor
-
bpy.ops.file.
unpack_all
(method='USE_LOCAL')¶ Unpack all files packed into this .blend to external ones
Parameters: method (enum in ['USE_LOCAL', 'WRITE_LOCAL', 'USE_ORIGINAL', 'WRITE_ORIGINAL', 'KEEP', 'REMOVE'], (optional)) – Method, How to unpack
-
bpy.ops.file.
unpack_item
(method='USE_LOCAL', id_name="", id_type=19785)¶ Unpack this file to an external file
Parameters: - method (enum in ['USE_LOCAL', 'WRITE_LOCAL', 'USE_ORIGINAL', 'WRITE_ORIGINAL'], (optional)) – Method, How to unpack
- id_name (string, (optional, never None)) – ID name, Name of ID block to unpack
- id_type (int in [0, inf], (optional)) – ID Type, Identifier type of ID block
-
bpy.ops.file.
unpack_libraries
()¶ Unpack all used Blender library files from this .blend file


Have you ever thought about how you learn? No, stop, I am actually asking you, have you ever actually sat down and thought about what’s the best learning environment for yourself. Well don’t feel bad, for me I definitely have not. If you say something like “who has the time,” “it’s not relevant to my success,” and “I just want to get things done.” Then you are very similar to me, as I have always thought that learning how I learn seemed very strange to me and think about everything else I could be getting done with this ‘wasted time.’ Nevertheless, when I actually did sit down and learned how I learn, I found it extremely beneficial to myself. Think about it, subconsciously you know what circumstances account to your best learning abilities, but have you ever heard the word or seen it on paper. No, but when you do it will change everything. If you want to find out for yourself take this quiz: Gregorc Thinking Style.
After I took Gregorc Thinking Style quiz, I discovered that my learning style is “Concrete Sequential.” I know those words don’t seem like much like now, but once I did a little research on what traits a concrete sequential learner has, I realized that it is exactly me.
Concrete sequential learners work best when they…
Like WOW, all of these describe my perfect learning environment, it’s crazy. Looking back on these past few weeks in DBC’s Phase-0, I have had my problems, who hasn’t. Other than the technical issues I encountered, there also are a few problems associated to my learning. These problems include: I always want to “have exact directions,” “face limited change,” and “can apply in a practical hand-on way.” These three have not only affected me in Phase-0, but also have plagued me for some time now. I like the ways I learn, am very stubborn at changing, and have always liked exact, predictable, and practical methods. The single biggest struggle for me has been not knowing what lies ahead. As I said, I am a very predictable and schedules person and if I do not know what lies ahead, I cannot plan my hours, and feel scattered. Fortunately, I have figured out how the next seven weeks will function, I am much more comfortable moving forward.
The problem with my mindset is that I have issues dealing with any other situation. I know I have this problem and I need to work on it. If I cannot find a way to adapt to other environments, I know I will have issues succeeding in my future. Since the first step is determining my style, next I need to act. By considering a fixed vs. Growth mindset approach, I need to establish a growth mindset and have to broaden the ways I learn and think.  Humans need to have flexibility and change in their lives or we will go nowhere. My plan is to once a week go out of my comfort zone and learn in a place I am not accustomed to. I might go to a coffee shop, or go outside, whatever really spark my mind and I am just going to roll with and not think about it. I believe this is an actionable, reasonable plan.
Although it can be tough to actually act upon it, it is good to know your personal learning capacity, the better-rounded you can become, the easier it will be to learn quickly and effectively. Our learning and thinking styles can morph and change as we exercise our brains. So after you take the quiz, think of some ways you can work to expand the ways you learn and think.


Reporters, students, others lose properties to fire in Bauchi
by Agency ReportAbdul-Saheed Olaide, a reporter with News Agency of Nigeria (NAN), and some of his neighbours lost their property in a fire that razed their residence in Gwalameji, a suburb of Bauchi, on Sunday afternoon.
The other victims are David Adenuga, a reporter with The Nation Newspapers, and some students of the Federal Polytechnic, Bauchi.
The victims said the source of the fire, which reportedly started at 1.30 p.m. from a bush behind the building was not known but that it destroyed nine rooms.
Mr Olaide said that the fire burnt his work tools and other valuables but expressed gratitude to God that he was still alive.
”I thank God for my life that it did not happen at night. It happened like a joke, many things have gone which I cannot mention right now,’’ he said.
Mr Adenuga said: ”It is like a dream. I cannot believe that everything in my room has gone. I lost all my belongings to the fire.
”There was no light at the time; we still don’t know the source of the fire.
“The fire affected nine rooms. It took the efforts of the Fire Service to put out the fire that already spread to other blocks,” he said.
Mr Adenuga said all his certificates and other valuables were burnt in the fire.
”I don’t know where to start, what to do; I don’t have anywhere to go. I am only left with the clothes on me,’’ he said.
A witness, Musa Sule, told reporters the incident started around 1:30p.m. from one of the rooms at Tinubu Lodge.
Mr Musa said cooking gas in the rooms might have contributed to the escalation of the fire, saying most of the rooms contained gas cylinders which exploded while the fire raged.
Another victim, Goodness Okpara, a student, said she was in the church when she received a call informing her of the incident.
“Actually, we are three occupants in the room. We were able to save our mattress and some things.’’
She, however, described the incident as an act of God. (NAN)


A user-assigned ID for the new, replacement order (like a purchase-order number assigned by a company). This ID is useful for recognizing future states related to this order. ClientOrderId defaults to 0.
Quantity to Display on the Market. If your order is for 1000, and you only want to show 100 at a time in market data, set this to 100. Set to 0 to display all
The ID of the instrument being traded.
When entering a Trailing Limit order, set this to offset the activation price. This allows you to activate your order away from the market.
The price at which to execute the new order, if the order is a Limit order.
The ID of the Order Management System on which the order is being canceled and replaced by another order.
One Cancels the Other — If the order being canceled in this call is order A, and the order replacing order A in this call is order B, then OrderIdOCO refers to an order C that is currently open. If order C executes, then order B is canceled. You can also set up order C to watch order B in this way, but that will require an update to order C.
The ID of the order to replace with this order.
The type of the replacement order.
When entering a stop/trailing order, set PegPriceType to the type of price that pegs the stop.
The amount of the order (buy or sell).
The side of the replacement order:
The price at which to execute the new order, if the order is a Stop order (either buy or sell).
The period during which the new order is executable.
There may be other settings for TimeInForce depending on the trading venue
The offset by which to trail the market in one of the trailing order types. Set this to the current price of the market to ensure that the trailing offset is the amount intended in a fast-moving market
Generated using TypeDoc
The ID of the account under which the original order was placed and the new order will be placed.
{number}
CancelReplaceOrderRequest


Recipe 20.6. Adding Functionality to a Class by Wrapping a MethodCredit: Ken Seehof, Holger Krekel ProblemYou need to add functionality to an existing class, without changing the source code for that class, and inheritance is not applicable (since it would make a new class, rather than changing the existing one). Specifically, you need to enrich a method of the class, adding some extra functionality "around" that of the existing method. SolutionAdding completely new methods (and other attributes) to an existing class object is quite simple, since the built-in function setattr does essentially all the work. We need to "decorate" an existing method to add to its functionality. To achieve this, we can build the new replacement method as a closure. The best architecture is to define general-purpose wrapper and unwrapper functions, such as: import inspect def wrapfunc(obj, name, processor, avoid_doublewrap=True): """ patch obj.<name> so that calling it actually calls, instead, processor(original_callable, *args, **kwargs) """ # get the callable at obj.<name> call = getattr(obj, name) # optionally avoid multiple identical wrappings if avoid_doublewrap and getattr(call, 'processor', None) is processor: return # get underlying function (if any), and anyway def the wrapper closure original_callable = getattr(call, 'im_func', call) def wrappedfunc(*args, **kwargs): return processor(original_callable, *args, **kwargs) # set attributes, for future unwrapping and to avoid double-wrapping wrappedfunc.original = call wrappedfunc.processor = processor # 2.4 only: wrappedfunc._ _name_ _ = getattr(call, '_ _name_ _', name) # rewrap staticmethod and classmethod specifically (iff obj is a class) if inspect.isclass(obj): if hasattr(call, 'im_self'): if call.im_self: wrappedfunc = classmethod(wrappedfunc) else: wrappedfunc = staticmethod(wrappedfunc) # finally, install the wrapper closure as requested setattr(obj, name, wrappedfunc) def unwrapfunc(obj, name): ''' undo the effects of wrapfunc(obj, name, processor) ''' setattr(obj, name, getattr(obj, name).original) This approach to wrapping is carefully coded to work just as well on ordinary functions (when obj is a module) as on methods of all kinds (e.g., bound methods, when obj is an instance; unbound, class, and static methods, when obj is a class). This method doesn't work when obj is a built-in type, though, because built-ins are immutable. For example, suppose we want to have "tracing" prints of all that happens whenever a particular method is called. Using the general-purpose wrapfunc function just shown, we could code: def tracing_processor(original_callable, *args, **kwargs): r_name = getattr(original_callable, '_ _name_ _', '<unknown>') r_args = map(repr, args) r_args.extend(['%s=%r' % x for x in kwargs.iteritems( )]) print "begin call to %s(%s)" % (r_name, ", ".join(r_args)) try: result = call(*args, **kwargs) except: print "EXCEPTION in call to %s" %(r_name,) raise else: print "call to %s result: %r" %(r_name, result) return result def add_tracing_prints_to_method(class_object, method_name): wrapfunc(class_object, method_name, tracing_processor) DiscussionThis recipe's task occurs fairly often when you're trying to modify the behavior of a standard or third-party Python module, since editing the source of the module itself is undesirable. In particular, this recipe can be handy for debugging, since the example function add_tracing_prints_to_method presented in the "Solution" lets you see on standard output all details of calls to a method you want to watch, without modifying the library module, and without requiring interactive access to the Python session in which the calls occur. You can also use this recipe's approach on a larger scale. For example, say that a library that you imported has a long series of methods that return numeric error codes. You could wrap each of them inside an enhanced wrapper method, which raises an exception when the error code from the original method indicates an error condition. Again, a key issue is not having to modify the library's own code. However, methodical application of wrappers when building a subclass is also a way to avoid repetitious code (i.e., boilerplate). For example, Recipe 5.12 and Recipe 1.24 might be recoded to take advantage of the general wrapfunc presented in this recipe. Particularly when "wrapping on a large scale", it is important to be able to "unwrap" methods back to their normal state, which is why this recipe's Solution also includes an unwrapfunc function. It may also be handy to avoid accidentally wrapping the same method in the same way twice, which is why wrapfunc supports the optional parameter avoid_doublewrap, defaulting to true, to avoid such double wrapping. (Unfortunately, classmethod and staticmethod do not support per-instance attributes, so the avoidance of double wrapping, as well as the ability to "unwrap", cannot be guaranteed in all cases.) You can wrap the same method multiple times with different processors. However, unwrapping must proceed last-in, first-out; as coded, this recipe does not support the ability to remove a wrapper from "somewhere in the middle" of a chain of several wrappers. A related limitation of this recipe as coded is that double wrapping is not detected when another unrelated wrapping occurred in the meantime. (We don't even try to detect what we might call "deep double wrapping.") If you need "generalized unwrapping", you can extend unwrap_func to return the processor it has removed; then you can obtain generalized unwrapping by unwrapping all the way, recording a list of the processors that you removed, and then pruning that list of processors and rewrapping. Similarly, generalized detection of "deep" double wrapping could be implemented based on this same idea. Another generalization, to fully support staticmethod and classmethod, is to use a global dict, rather than per-instance attributes, for the original and processor values; functions, bound and unbound methods, as well as class methods and static methods, can all be used as keys into such a dictionary. Doing so obviates the issue with the inability to set per-instance attributes on class methods and static methods. However, each of these generalizations can be somewhat complicated, so we are not pursuing them further here. Once you have coded some processors with the signature and semantics required by this recipe's wrapfunc, you can also use such processors more directly (in cases where modifying the source is OK) with a Python 2.4 decorator, as follows: def processedby(processor): """ decorator to wrap the processor around a function. """ def processedfunc(func): def wrappedfunc(*args, **kwargs): return processor(func, *args, **kwargs) return wrappedfunc return processedfunc For example, to wrap this recipe's tracing_processor around a certain method at the time the class statement executes, in Python 2.4, you can code: class SomeClass(object): @processedby(tracing_processor) def amethod(self, s): return 'Hello, ' + s See AlsoRecipe 5.12 and Recipe 1.24 provide examples of the methodical application of wrappers to build a subclass to avoid boilerplate; Library Reference and Python in a Nutshell docs on built-in functions getattr and setattr and module inspect. |


Utilities: Visibility
CSS visibility override classes. Snippets below demonstrate utility styling.
.u-visibility-visible
Visible Text
.u-visibility-hidden
This hidden textHidden Texttakes up space.
.u-visibility-screenreader
Focusabled text with hidden screenreader text.
Hidden Screenreader accessible text


Computes 46 optimized distance and similarity measures for comparing probability functions. These comparisons between probability functions have their foundations in a broad range of scientific disciplines from mathematics to ecology. The aim of this package is to provide a core framework for clustering, classification, statistical inference, goodness-of-fit, non-parametric statistics, information theory, and machine learning tasks that are based on comparing univariate or multivariate probability functions.
| Version: | 0.2.0 |
| Depends: | R (≥ 3.1.2) |
| Imports: | Rcpp, dplyr, KernSmooth |
| LinkingTo: | Rcpp |
| Suggests: | testthat, knitr |
| Published: | 2018-05-22 |
| Author: | Hajk-Georg Drost [aut, cre] |
| Maintainer: | Hajk-Georg Drost <hgd23 at cam.ac.uk> |
| License: | GPL-2 |
| URL: | https://github.com/HajkD/philentropy |
| NeedsCompilation: | yes |
| Materials: | README NEWS |
| CRAN checks: | philentropy results |
| Reference manual: | philentropy.pdf |
| Vignettes: |
Distances Information Theory Introduction |
| Package source: | philentropy_0.2.0.tar.gz |
| Windows binaries: | r-devel: philentropy_0.2.0.zip, r-release: philentropy_0.2.0.zip, r-oldrel: philentropy_0.2.0.zip |
| OS X binaries: | r-release: philentropy_0.2.0.tgz, r-oldrel: philentropy_0.2.0.tgz |
| Old sources: | philentropy archive |
Please use the canonical form https://CRAN.R-project.org/package=philentropy to link to this page.


Deshaun Watson shares details of postgame exchange with Lamar Jackson, with MVP talk included
by TSD StaffTexans quarterback Deshaun Watson and Ravens signal-caller Lamar Jackson are competing against each other for the league’s MVP award, but it’s all love between the two young stars.
It was Jackson who came out on top during Sunday’s game — as he’s done over the past month, having beaten Watson, Russell Wilson and Tom Brady — with the Ravens destroying the Texans, 41-7.
Still, the two quarterbacks shared a warm embrace after the game, with an interesting conversation as well. They even swapped jerseys on the field, swarmed by reporters and photographers.
Watson shared what the two talked about after the game, and even revealed that he wrote “MVP” on Jackson’s jersey.
Well, it appears Jackson has Watson’s vote for MVP. He does appear to be the current leader for the award, with Wilson right behind him.


LifeStyle Store
Sign-up
Log-in
Contact us
First Name
Last Name
Country
Mumbai
Banglore
Delhi
Subject


| User Score: |
|
|
| 1. User Name |
%username% |
| 2. User Email |
%useremail% |
| 3. User Title |
%usertitle% |
| 4. Department |
%userdepartment% |
| 5. Employee Type |
%usertype% |
| 6. Phone |
%userphone% |
| 7. Cube Location |
%userlocation% |
| 8. City/State |
%usercitystate% |
| 9. Manager |
%managername% |
| 10. Manager Title |
%managertitle% |
| 11. Manager Email |
%manageremail% |
| 12. Manager Phone |
%managerphone% |
|
| Machine Score: |
|
|
|
| 1. Machine Name |
%machinename% : %srcip% |
| 2. OS |
%machineos% |
| 3. Domain |
%machinedomain% |
| 4. Patches (critical-high-low) |
%criticalpatches%, %highpatches%, %lowpatches% |
| 5. AV Installed |
%avinstalled% |
| 6. AV Running |
%avrunning% |
| 7. AV Definition Version |
%avdefversion% |
| 8. Bit9 Installed |
%bit9installed% |
| 9. Bit9 Running |
%bit9running% |
| 10. Hostname Validated: |
|
| 11. Hostname Validation Method: |
|
| 12. Last Update Time: |
%clientlastupdate% |
|


想要什么，现在就去创造
We can give your company superpowers to do things that they never thought possible. Let us delight your customers and empower your needs...through pure data analytics.
Yes that's right, you thought it was the stuff of dreams, but even bananas can be bioengineered.
That is what they all say about us
Nan Chief Fun Officer Acme Toys


Touching your face makes it more likely you'll contract COVID-19!

You can run this in the background, but it needs to be in its own window
rather than a tab.
It looks like you're using Safari! If you're not hearing any audio, select the "Safari" menu, then "Settings for This Website". Set the "Auto-Play" dropdown to "Allow All Auto-Play" [x]
All processing happens in your web browser.
Your webcam data does
not leave your computer.
Not working very well? Help improve quality by spending ~2 minutes to provide some training data.


System Architect Picture "Partitive Subject Relation"
Parent Diagram:
Inter Subject Relationship
(OMT Object Model)


Live Data:
Alberta
| Infected | Death |
|---|---|
British Columbia
| Infected | Death |
|---|---|
Manitoba
| Infected | Death |
|---|---|
New Brunswick
| Infected | Death |
|---|---|
Ontario
| Infected | Death |
|---|---|
Quebec
| Infected | Death |
|---|---|
Nova Scotia
| Infected | Death |
|---|---|
Prince Edward Island
| Infected | Death |
|---|---|
Saskatchewan
| Infected | Death |
|---|---|
Newfoundland and Labrador
| Infected | Death |
|---|---|
Yukun
| Infected | Death |
|---|---|
Northwest Territories
| Infected | Death |
|---|---|
Nunavut
| Infected | Death |
|---|---|


+++ title = "Potosí" lat = -19.590000 lon = -65.750000 +++
Potosí is part of the historic, colonial south-west of Bolivia; and it's a prime stop on the Bolivian gringo trail, due to its famous 400-year-old mines in the nearby mountain of Cerro Rico. Potosí also claims to be the world's highest city. It's a nice place, and for most of the day and evening, it's quite lively and has a good atmosphere. Quite cold, though.


Preston McDonald's Portfolio
This is my portfolio.
Hello! My name is Preston mcDonald and I am a participant of Google's Software Product Sprint Program. I am currently a sophomore studying computer sience and psychology at Duke University. I enjoy using my knowledge to promote social good in my community. Outside of my studies I am enjoy playing soccer, excercising, and spending time with my friends and family.
Click here to get a random message:
A few of the projects I have worked on for my classes include:
- A recommender program in python
- A cache simulator in C
- An austocomplete program in Java
If you want to learn more about me, click on the links below!
Visit my GitHub Visit my linkedin


|
RandomLib
|
The exponential distribution for MPFR (the log method). More...
#include <RandomLib/MPFRExponentialL.hpp>
Public Member Functions | |
| MPFRExponentialL () | |
| ~MPFRExponentialL () | |
| int | operator() (mpfr_t val, gmp_randstate_t r, mpfr_rnd_t round) const |
The exponential distribution for MPFR (the log method).
This class is DEPRECATED. It is included for illustrative purposes only. The MPFRExponential class provides a much more efficient method for sampling from the exponential distribution.
This is an adaption of ExponentialDistribution to MPFR. The changes are
This class uses mutable private objects. So a single MPFRExponentialL object cannot safely be used by multiple threads. In a multi-processing environment, each thread should use a thread-specific MPFRExponentialL object.
Definition at line 39 of file MPFRExponentialL.hpp.
| RandomLib::MPFRExponentialL::MPFRExponentialL | ( | ) | [inline] |
Initialize the MPFRExponentialL object.
Definition at line 48 of file MPFRExponentialL.hpp.
| RandomLib::MPFRExponentialL::~MPFRExponentialL | ( | ) | [inline] |
Destroy the MPFRExponentialL object.
Definition at line 57 of file MPFRExponentialL.hpp.
| int RandomLib::MPFRExponentialL::operator() | ( | mpfr_t | val, |
| gmp_randstate_t | r, | ||
| mpfr_rnd_t | round | ||
| ) | const [inline] |
Sample from the exponential distribution with mean 1.
| [out] | val | the sample from the exponential distribution |
| [in,out] | r | a GMP random generator. |
| [in] | round | the rounding direction. |
Definition at line 72 of file MPFRExponentialL.hpp.


Senior Civil Service Come and lead the future of the Civil Service
The Civil Service plays a crucial role in supporting the wellbeing, security and prosperity of the country.
The Senior Civil Service is looking for people who have ambition, motivation and passion. You will be leading some of Europe’s largest projects, changing the way the public interacts with government services and transforming the way we use data and technology to build a Civil Service for the future.
The Senior Civil Service provides high-level support to government ministers, assists in the development and implementation of policy and delivers safe and secure public services to our citizens.
This is an opportunity to join government at an incredibly interesting time. It’s one of the most challenging and rewarding places to work in the UK today. We need a unique combination of leadership and hands-on technical expertise to lead our digital transformation.
We employ 3,900 professionals at this level, in 55 different government departments and agencies
{% include "includes/call_to_action.html" %}


| < Day Day Up > |
11.7. Building Your Own Lisp LibraryAfter you have become proficient at Emacs Lisp programming, you will want a library of Lisp functions and packages that you can call up from Emacs at will. Of course, you can define a few small functions in your .emacs file, but if you are writing bigger pieces of code for more specialized purposes, you will not want to clutter up your .emacs fileónor will you want Emacs to spend all that time evaluating the code each time you start it up. The answer is to build your own Lisp library, analogous to the Lisp directories that come with Emacs and contain all of its built-in Lisp code. After you have created a library, you can load whatever Lisp packages you need at a given time and not bother with the others. Creating a library requires two simple steps. First, create a directory in which your Lisp code will reside. Most people create a elisp subdirectory of their home directory. Lisp files are expected to have names ending in .el (your .emacs file is an exception). The second step is to make your directory known to Emacs so that when you try to load a Lisp package, Emacs knows where to find it. Emacs keeps track of such directories in the global variable load-path, which is a list of strings that are directory names. The initial value for load-path is populated with the names of the Lisp directories that come with Emacs, e.g., /usr/local/emacs/lisp. You will need to add the name of your own Lisp directory to load-path. One way to make this addition is to use the Lisp function append, which concatenates any number of list arguments together. For example, if your Lisp directory is ~<yourname>/lisp, you would put the following in your .emacs file: (setq load-path (append load-path (list "~yourname/lisp"))) The function list is necessary because all of the arguments to append must be lists. This line of code must precede any commands in your .emacs file that load packages from your Lisp directory. When you load a library, Emacs searches directories in the order in which they appear in load-path; therefore, in this case, Emacs searches its default Lisp directory first. If you want your directory to be searched first, you should use the cons function described earlier instead of append, as follows: (setq load-path (cons "~yourname/lisp" load-path)) This form is useful if you want to replace one of the standard Emacs packages with one of your own. For example, you'd use this form if you've written your own version of C mode and want to use it instead of the standard package. Notice that the directory name here is not surrounded by a call to list because cons's first argument can be an atom (a string in this case). This situation is similar to the use of cons for pushing values onto stacks, as in the calculator mode described earlier. If you want Emacs to search the directory you happen to be in at any given time, simply add nil to load-path, either by prepending it via cons or by appending it via append. Taking this step is analogous to putting . in your Unix PATH environment variable. After you have created a private Lisp library and told Emacs where to find it, you're ready to load and use the Lisp packages that you've created. There are several ways of loading Lisp packages into Emacs. The first of these should be familiar from Chapter 10:
11.7.1 Byte-Compiling Lisp FilesAfter you have created your Lisp directory, you can make loading and running your Lisp files more efficient by byte-compiling them, or translating their code into byte code, a more compact, machine-readable form. Byte-compiling the Lisp file filename.el creates the byte code file filename.elc. Byte code files are typically 40 to 75 percent of the size of their non-byte-compiled counterparts. Although byte-compiled files are more efficient, they are not strictly necessary. The load-library command, when given the argument filename, first looks for a file called <filename>.elc. If that doesn't exist, it tries <filename>.el, that is, the non-byte-compiled version. If that doesn't exist, it finally tries just <filename>. Thus, you can byte-compile your .emacs file, which may result in faster startup if your .emacs is large. You can byte-compile a single function in a buffer of Lisp code by placing your cursor anywhere in the function and typing M-x compile-defun. You can byte-compile an entire file of Lisp by invoking M-x byte-compile-file Enter and supplying the filename. If you omit the .el suffix, Emacs appends it and asks for confirmation. If you have changed the file but have not saved it, Emacs offers to save it first. Then you will see an entertaining little display in the minibuffer as the byte-compiler does its work: the names of functions being compiled flash by. The byte-compiler creates a file with the same name as the original Lisp file but with c appended; thus, <filename>.el becomes <filename>.elc, and .emacs becomes .emacs.elc. Finally, if you develop a directory with several Lisp files, and you make changes to some of them, you can use the byte-recompile-directory command to recompile only those Lisp files that have been changed since being byte-compiled (analogously to the Unix make utility). Just type M-x byte-recompile-directory Enter and supply the name of the Lisp directory or just press Enter for the default, which is the current directory. |
| < Day Day Up > |


A look the various ways the IoT asks consumers to think like programmers, and the risks inherent in exponentially increasing educators.Continue reading UX challenges in the Internet of Things.


|
Hull Abstraction
Center of Advanced Robotics
|
The Preprocessor class. More...
#include <preprocessor.h>
Public Member Functions | |
| Preprocessor () | |
| Construct a new Preprocessor object. More... | |
| ~Preprocessor () | |
| Destroy the Preprocessor object. More... | |
| void | voxelGridFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implementation of the voxel grid filter to perform down sampling. More... | |
| void | statisticalFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Remove outliers through the statitical filter. More... | |
| void | passThroughFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implement the pass-through filter. More... | |
| void | conditionalFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implement the conditional filter. More... | |
| void | radiusFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implement the radius filter. More... | |
| void | appendNormalEstimation (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointNormal >::Ptr cloud_with_normals) |
| Estimate normals and append those to the input cloud. More... | |
| void | movingLeastSquares (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr smoothed_cloud, pcl::PointCloud< pcl::PointNormal >::Ptr smoothed_cloud_with_normals) |
| Perform MLS (Moving Least Squares) method for data smoothing and normal estimation. More... | |
| Preprocessor () | |
| Construct a new Preprocessor object. More... | |
| ~Preprocessor () | |
| Destroy the Preprocessor object. More... | |
| void | voxelGridFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implementation of the voxel grid filter to perform down sampling. More... | |
| void | statisticalFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Remove outliers through the statitical filter. More... | |
| void | passThroughFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implement the pass-through filter. More... | |
| void | conditionalFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implement the conditional filter. More... | |
| void | radiusFilter (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr filtered_cloud) |
| Implement the radius filter. More... | |
| void | appendNormalEstimation (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointNormal >::Ptr cloud_with_normals) |
| Estimate normals and append those to the input cloud. More... | |
| void | movingLeastSquares (pcl::PointCloud< pcl::PointXYZ >::Ptr cloud, pcl::PointCloud< pcl::PointXYZ >::Ptr smoothed_cloud, pcl::PointCloud< pcl::PointNormal >::Ptr smoothed_cloud_with_normals) |
| Perform MLS (Moving Least Squares) method for data smoothing and normal estimation. More... | |
Private Attributes | |
| pcl::ApproximateVoxelGrid< pcl::PointXYZ > | approximate_voxel_grid |
| pcl::StatisticalOutlierRemoval< pcl::PointXYZ > | statistical_outlier_removal |
| pcl::PassThrough< pcl::PointXYZ > | pass_through |
| pcl::ConditionalRemoval< pcl::PointXYZ > | conditional_removal |
| pcl::RadiusOutlierRemoval< pcl::PointXYZ > | radius_outlier_removal |
| pcl::NormalEstimation< pcl::PointXYZ, pcl::Normal > | normal_estimation |
| pcl::MovingLeastSquares< pcl::PointXYZ, pcl::PointNormal > | moving_least_squares |
| pcl::PointCloud< pcl::PointNormal > | mls_points |
The Preprocessor class.
This class wraps some preprocessing methods for point cloud data
|
inline |
Construct a new Preprocessor object.
|
inline |
Destroy the Preprocessor object.
|
inline |
Construct a new Preprocessor object.
|
inline |
Destroy the Preprocessor object.
| void hull_abstraction::Preprocessor::appendNormalEstimation | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointNormal >::Ptr | cloud_with_normals | ||
| ) |
Estimate normals and append those to the input cloud.
| [in] | cloud | Cloud of PointXYZ |
| [out] | cloud_with_normals | Cloud of PointNormal |
| void hull_abstraction::Preprocessor::appendNormalEstimation | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointNormal >::Ptr | cloud_with_normals | ||
| ) |
Estimate normals and append those to the input cloud.
| [in] | cloud | Cloud of PointXYZ |
| [out] | cloud_with_normals | Cloud of PointNormal |
| void hull_abstraction::Preprocessor::conditionalFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implement the conditional filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::conditionalFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implement the conditional filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::movingLeastSquares | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | smoothed_cloud, | ||
| pcl::PointCloud< pcl::PointNormal >::Ptr | smoothed_cloud_with_normals | ||
| ) |
Perform MLS (Moving Least Squares) method for data smoothing and normal estimation.
| [in] | cloud | Cloud of PointXYZ |
| [out] | smoothed_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::movingLeastSquares | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | smoothed_cloud, | ||
| pcl::PointCloud< pcl::PointNormal >::Ptr | smoothed_cloud_with_normals | ||
| ) |
Perform MLS (Moving Least Squares) method for data smoothing and normal estimation.
| [in] | cloud | Cloud of PointXYZ |
| [out] | smoothed_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::passThroughFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implement the pass-through filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::passThroughFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implement the pass-through filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::radiusFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implement the radius filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::radiusFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implement the radius filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::statisticalFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Remove outliers through the statitical filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::statisticalFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Remove outliers through the statitical filter.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::voxelGridFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implementation of the voxel grid filter to perform down sampling.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
| void hull_abstraction::Preprocessor::voxelGridFilter | ( | pcl::PointCloud< pcl::PointXYZ >::Ptr | cloud, |
| pcl::PointCloud< pcl::PointXYZ >::Ptr | filtered_cloud | ||
| ) |
Implementation of the voxel grid filter to perform down sampling.
| [in] | cloud | Cloud of PointXYZ |
| [out] | filtered_cloud | Cloud of PointXYZ |
|
private |
Object for approximate voxel grid
|
private |
Object for conditional removal
|
private |
Point cloud used to stored the result of MLS
|
private |
Object for moving least squares method
|
private |
Object for normal estimation
|
private |
Object for pass-through filter
|
private |
Object for radius outlier removal
|
private |
Object for statistical outlier removal


SingleRowDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)> Methods
The SingleRowDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)> type exposes the following members.
Methods
| Name | Description | |
|---|---|---|
| AsNonQuery |
Indicates this operation has no result set.
(Inherited from DbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| Equals(System.Object) |
Determines whether the specified object is equal to the current object. (Inherited from Object.) |
|
| Execute |
Execute the operation synchronously.
(Inherited from DbCommandBuilder.) |
|
| ExecuteAsync(Object) |
Execute the operation asynchronously.
(Inherited from DbCommandBuilder.) |
|
| ExecuteAsync(CancellationToken, Object) |
Execute the operation asynchronously.
(Inherited from DbCommandBuilder.) |
|
| Finalize |
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.) |
|
| GetHashCode |
Serves as the default hash function. (Inherited from Object.) |
|
| GetType |
Gets the Type of the current instance. (Inherited from Object.) |
|
| MemberwiseClone |
Creates a shallow copy of the current Object. (Inherited from Object.) |
|
| Prepare |
Prepares the command for execution by generating any necessary SQL.
(Inherited from DbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToBoolean()()()() |
Indicates the results should be materialized as a Boolean.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToBoolean(String) |
Indicates the results should be materialized as a Boolean.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToBooleanOrNull()()()() |
Indicates the results should be materialized as a nullable Boolean.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToBooleanOrNull(String) |
Indicates the results should be materialized as a nullable Boolean.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToByte()()()() |
Indicates the results should be materialized as a byte.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToByte(String) |
Indicates the results should be materialized as a byte.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToByteArray()()()() |
Indicates the results should be materialized as a byte array.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToByteArray(String) |
Indicates the results should be materialized as a byte array.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToByteOrNull()()()() |
Indicates the results should be materialized as a nullable byte.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToByteOrNull(String) |
Indicates the results should be materialized as a nullable byte.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDataRow |
Indicates the results should be materialized as a Row.
|
|
| ToDateTime()()()() |
Indicates the results should be materialized as a DateTime.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDateTime(String) |
Indicates the results should be materialized as a DateTime.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDateTimeOffset()()()() |
Indicates the results should be materialized as a DateTimeOffset.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDateTimeOffset(String) |
Indicates the results should be materialized as a DateTimeOffset.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDateTimeOffsetOrNull()()()() |
Indicates the results should be materialized as a nullable DateTimeOffset.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDateTimeOffsetOrNull(String) |
Indicates the results should be materialized as a nullable DateTimeOffset.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDateTimeOrNull()()()() |
Indicates the results should be materialized as a nullable DateTime.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDateTimeOrNull(String) |
Indicates the results should be materialized as a nullable DateTime.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDecimal()()()() |
Indicates the results should be materialized as a Decimal.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDecimal(String) |
Indicates the results should be materialized as a Decimal.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDecimalOrNull()()()() |
Indicates the results should be materialized as a nullable Decimal.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDecimalOrNull(String) |
Indicates the results should be materialized as a nullable Decimal.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDouble()()()() |
Indicates the results should be materialized as a Double.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDouble(String) |
Indicates the results should be materialized as a Double.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDoubleOrNull()()()() |
Indicates the results should be materialized as a nullable Double.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDoubleOrNull(String) |
Indicates the results should be materialized as a nullable Double.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToDynamicObject |
Materializes the result as a dynamic object
|
|
| ToGuid()()()() |
Indicates the results should be materialized as a Guid.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToGuid(String) |
Indicates the results should be materialized as a Guid.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToGuidOrNull()()()() |
Indicates the results should be materialized as a nullable Guid.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToGuidOrNull(String) |
Indicates the results should be materialized as a nullable Guid.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt16()()()() |
Indicates the results should be materialized as a Int16.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt16(String) |
Indicates the results should be materialized as a Int16.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt16OrNull()()()() |
Indicates the results should be materialized as a nullable Int16.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt16OrNull(String) |
Indicates the results should be materialized as a nullable Int16.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt32()()()() |
Indicates the results should be materialized as a Int32.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt32(String) |
Indicates the results should be materialized as a Int32.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt32OrNull()()()() |
Indicates the results should be materialized as a nullable Int32.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt32OrNull(String) |
Indicates the results should be materialized as a nullable Int32.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt64()()()() |
Indicates the results should be materialized as a Int64.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt64(String) |
Indicates the results should be materialized as a Int64.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt64OrNull()()()() |
Indicates the results should be materialized as a nullable Int64.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToInt64OrNull(String) |
Indicates the results should be materialized as a nullable Int64.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToObject<(Of <<'(TObject>)>>) |
Materializes the result as an instance of the indicated type
|
|
| ToRow |
Indicates the results should be materialized as a Row.
|
|
| ToSingle()()()() |
Indicates the results should be materialized as a Single.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToSingle(String) |
Indicates the results should be materialized as a Single.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToSingleOrNull()()()() |
Indicates the results should be materialized as a nullable Single.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToSingleOrNull(String) |
Indicates the results should be materialized as a nullable Single.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToString()()()() |
Indicates the results should be materialized as a nullable string.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToString(String) |
Indicates the results should be materialized as a nullable string.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToTimeSpan()()()() |
Indicates the results should be materialized as a TimeSpan.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToTimeSpan(String) |
Indicates the results should be materialized as a TimeSpan.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToTimeSpanOrNull()()()() |
Indicates the results should be materialized as a nullable TimeSpan.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToTimeSpanOrNull(String) |
Indicates the results should be materialized as a nullable TimeSpan.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToXml()()()() |
Materializes the result as an XElement.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| ToXml(String) |
Materializes the result as an XElement.
(Inherited from ScalarDbCommandBuilder<(Of <(<'TCommand, TParameter>)>)>.) |
|
| TryGetColumn |
Returns the column associated with the column name.
(Inherited from DbCommandBuilder.) |