LifeViewer/Known bugs/Scripting: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 55: | Line 55: | ||
* Attempting to customize the colour of GRIDMAJOR in a hexagonal or triangular rule, or a square grid rule with a GRIDMAJOR interval of 0, will not display an error. | * Attempting to customize the colour of GRIDMAJOR in a hexagonal or triangular rule, or a square grid rule with a GRIDMAJOR interval of 0, will not display an error. | ||
** This is unlike when trying to color cell states which do not apply to the active rule, as well as bounded grid edge cells in rules which do not specify a bounded grid; both cases produce an error to indicate that the customization is irrelevant. | ** This is unlike when trying to color cell states which do not apply to the active rule, as well as bounded grid edge cells in rules which do not specify a bounded grid; both cases produce an error to indicate that the customization is irrelevant. | ||
** In the former two cases a custom theme is also created. | |||
{| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | {| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | ||
! Hexagonal | ! Hexagonal | ||
Latest revision as of 11:39, 14 July 2026
Currently known issues with LifeViewer script commands.
- STATE1FIT does not work as expected in [R]Super rules.
- STATE1FIT may be deprecated in the future in favor of a new ALIVEFIT command in order to resolve this issue.[1]
| [R]Standard | [R]History |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
| [R]Super | [R]Investigator |
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- Setting up paste commands that cancel out to produce nothing will have differing results in the range-1 algorithm versus the general-range algorithm.
- At T=0, in the range-1 algorithm, a dead cell is visible in the thumbnail, but is not present in the popup viewer; in the general-range algorithm, it is present in both cases. In both cases, dead cells will manifest from T=1 onwards.
| Standard | General |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- Attempting to customize the colour of GRIDMAJOR in a hexagonal or triangular rule, or a square grid rule with a GRIDMAJOR interval of 0, will not display an error.
- This is unlike when trying to color cell states which do not apply to the active rule, as well as bounded grid edge cells in rules which do not specify a bounded grid; both cases produce an error to indicate that the customization is irrelevant.
- In the former two cases a custom theme is also created.
| Hexagonal | Triangular | GRIDMAJOR 0 |
|---|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- Changing the color of "dead" in [R]Super or [R]Investigator will not change the color of any cell states. However, it also will not display an error indicating that "dead" is not a valid element to customize for these specific rules.
- In [R]Standard and [R]History, "dead" will affect the colors of freshly-dead cells.
- Attempting to customize the capitalized "DEAD" in [R]Super or [R]Investigator will display an error.
| [R]Standard | [R]History |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
| [R]Super | [R]Investigator |
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- Trying to change the colour of DEAD in a Generations rule with 255 or 256 states, or DEADRAMP in a rule with 256 states, will change nothing, however, again, no error is produced indicating that these are invalid to customize.
- A custom theme is also created when it should not be.
| G255 | G256 |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- Trying to change the colour of DEAD in a rule with HISTORYSTATES 0 or 1, DEADRAMP in a rule with HISTORYSTATES 0, or ALIVERAMP in a rule with AGESTATES 0, will change nothing, however, yet again, no error is produced indicating that these are invalid to customize.
- Custom themes are also created as a result.
- In Help > Themes, the values for DEAD, DEADRAMP and ALIVERAMP are all also still present, rather than being eliminated due to their absence in such cases.
- Bizarrely, for HISTORYSTATES 1, despite DEADRAMP being used, the colour for DEAD is instead shown in Help > Info > Cells (matching any custom specifications), with DEADRAMP, the colour which is actually in use, being absent.
| HISTORYSTATES 1 | HISTORYSTATES 0 | AGESTATES 0 |
|---|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- Different errors will be produced when trying to customize the colors of history, mark1, markoff, mark2 and kill in a rulespace which does not support these states if they are specified as lowercase compared to uppercase.
| Lowercase | Uppercase |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- When changing the active theme, TRACKLOOP will not adjust, resulting in visual major grid line jumping.
- For the following, change the theme to a theme with major grid lines such as the MCell theme.
| (click above to open LifeViewer) |
- Pasting something in [R]History via PASTEMODE COPY will cause any state-0 cells to become freshly-created state 2 cells.
- This is in contract to pasting state-2 cells themselves: these are set as fully aged.
- Expected behaviour would be for state 0 cells to be pasted as state 0 cells.
| Input pattern | When pasted |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- If a pattern that uses HISTORYFIT has its evolution modified by PASTE or Kill Gliders in a certain way, AUTOFIT will ignore all preceding history cells when calculating the box to fit the pattern to.
| PASTE | Kill Gliders |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- User interfaces interact incorrectly with specific values for popup width and height as defined in script commands.
- On some touchscreen devices, the popup created by the right thumbnail is twice the size it should be.[2]
- If a viewer window has a height of below 480, the Settings button will be disabled as the contents of that menu would not display in a usable way. Maximizing the popup on the right will enable that button, allowing it to be entered, and un-maximizing the popup will result in the settings menu closing. However, it may remain open for one frame before closing, showing buttons in an intersecting state.
| normal popup size | atypical size |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |
- If some commands are provided with a value exceeding 2147483647, they will overflow, rather than rejecting the value as it is provided. This does not apply to all commands.
- These values are presumably those which are handled as Uint32Arrays.[3]
| rejects correctly | incorrectly overflows |
|---|---|
(click above to open LifeViewer) |
(click above to open LifeViewer) |