Table Driven Entries and Dynamic Table Columns: Difference between revisions
Jump to navigation
Jump to search
m (1 revision(s)) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Table driven entry will no longer cause crash if the "_time"<br /> column is no longer valid. However it will NOT track movement of the time column once the run has started. | |||
Hence if using dynamic columns with table driven entries: | Hence if using dynamic columns with table driven entries: | ||
*Ensure the time column ends up in the original position as at the<br /> start of the run whenever columns are manipulated | *Ensure the time column ends up in the original position as at the<br /> start of the run whenever columns are manipulated | ||
*Dont manipulate columns in the table unless the table is empty (no rows) | *Dont manipulate columns in the table unless the table is empty (no rows) otherwise the table driven entry may produce unexpected items. | ||
---- | |||
<font size="2">idkbase note 11</font> | |||
[[Category:Table]] | [[Category:Table]] | ||
[[Category:Object/Entry]] | [[Category:Object/Entry]] | ||
[[Category: | [[Category:Item]] | ||
[[Category:Runtime Engine]] | |||
Latest revision as of 21:52, 12 January 2008
Table driven entry will no longer cause crash if the "_time"
column is no longer valid. However it will NOT track movement of the time column once the run has started.
Hence if using dynamic columns with table driven entries:
- Ensure the time column ends up in the original position as at the
start of the run whenever columns are manipulated - Dont manipulate columns in the table unless the table is empty (no rows) otherwise the table driven entry may produce unexpected items.
idkbase note 11