LifeViewer/Known bugs/Scripting: Difference between revisions
Jump to navigation
Jump to search
Created page with "* 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.<ref name="bbissues">https://conwaylife.com/forums/viewtopic.php?p=158545#p158569</ref> {| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" ! [R]Standard ! [R]History |- | {{EmbedViewer |rle = x = 3, y = 3, rule = B3/S23 o$obo$2o! |viewerconfig = #C AUTOFIT STATE1FIT T..." |
No edit summary |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Currently known issues with LifeViewer script commands.<!--to add: pasting history cells in hex/tri visibility discrepancy, which reoccurred--> | |||
* STATE1FIT does not work as expected in [R]Super rules. | * 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.<ref name="bbissues">https://conwaylife.com/forums/viewtopic.php?p=158545#p158569</ref> | ** STATE1FIT may be deprecated in the future in favor of a new ALIVEFIT command in order to resolve this issue.<ref name="bbissues">https://conwaylife.com/forums/viewtopic.php?p=158545#p158569</ref> | ||
| Line 34: | Line 36: | ||
* Setting up paste commands that cancel out to produce nothing will have differing results in the range-1 algorithm versus the general-range algorithm. | * 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. | ** 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. | ||
{| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | {| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | ||
! Standard | ! Standard | ||
| Line 50: | Line 51: | ||
}} | }} | ||
|} | |} | ||
* 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 | ||
| Line 74: | Line 77: | ||
}} | }} | ||
|} | |} | ||
* 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. | * 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. | ||
| Line 107: | Line 111: | ||
}} | }} | ||
|} | |} | ||
* 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. | |||
{| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | |||
! G255 | |||
! G256 | |||
|- | |||
| {{EmbedViewer | |||
|rle = x = 2, y = 2, rule = /2/255 | |||
AB$AB! | |||
|viewerconfig = #C [[ STARTFROM 256 COLOR DEAD Blue THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
| {{EmbedViewer | |||
|rle = x = 2, y = 2, rule = /2/256 | |||
AB$AB! | |||
|viewerconfig = #C [[ STARTFROM 256 COLOR DEAD Blue COLOR DEADRAMP Green THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
|} | |||
* 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. | |||
{| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | |||
! HISTORYSTATES 1 | |||
! HISTORYSTATES 0 | |||
! AGESTATES 0 | |||
|- | |||
| {{EmbedViewer | |||
|rle = x = 2, y = 4, rule = B2/S | |||
bo$o$o$bo! | |||
|viewerconfig = #C [[ THEME Blues STARTFROM 5 HISTORYSTATES 1 COLOR DEAD Green THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
| {{EmbedViewer | |||
|rle = x = 2, y = 4, rule = B2/S | |||
bo$o$o$bo! | |||
|viewerconfig = #C [[ THEME Blues STARTFROM 5 HISTORYSTATES 0 COLOR DEAD Green COLOR DEADRAMP Red THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
| {{EmbedViewer | |||
|rle = x = 1, y = 3, rule = B3/S23 | |||
o$o$o! | |||
|viewerconfig = #C [[ THEME Blues STARTFROM 5 AGESTATES 0 COLOR ALIVERAMP Green THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
|} | |||
* 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. | * 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. | ||
| Line 124: | Line 175: | ||
}} | }} | ||
|} | |} | ||
* When changing the active theme, TRACKLOOP will not adjust, resulting in visual major grid line jumping. | * When changing the active theme, TRACKLOOP will not adjust, resulting in visual major grid line jumping. | ||
| Line 133: | Line 185: | ||
|viewerconfig = [[ AUTOSTART THEME Margolus GRID TRACKLOOP 4 -1/4 1/4 GPS 5 ]] | |viewerconfig = [[ AUTOSTART THEME Margolus GRID TRACKLOOP 4 -1/4 1/4 GPS 5 ]] | ||
}} | }} | ||
* Pasting something in [R]History via PASTEMODE COPY will cause any state-0 cells to become freshly-created state 2 cells. | * Pasting something in [R]History via PASTEMODE COPY will cause any state-0 cells to become freshly-created state 2 cells. | ||
| Line 152: | Line 205: | ||
}} | }} | ||
|} | |} | ||
* 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. | |||
{| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | |||
! PASTE | |||
! Kill Gliders | |||
|- | |||
| {{EmbedViewer | |||
|rle = x = 60, y = 3, rule = B3/S23 | |||
obo54bobo$b2o54b2o$bo56bo! | |||
|viewerconfig = #C [[ AUTOSTART AUTOFIT HISTORYFIT PASTEMODE XOR PASTET 200 PASTE o! 37 27 THEME Book THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
| {{EmbedViewer | |||
|rle = x = 10, y = 75, rule = B3/S23 | |||
obo$3bo$3bo5bo$o2bo3bobo$b3o4b2o67$4b2o$4bo$5b3o$7bo! | |||
|viewerconfig = #C [[ AUTOSTART AUTOFIT HISTORYFIT KILLGLIDERS THEME Book THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
|} | |||
* 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.<ref>https://conwaylife.com/forums/viewtopic.php?p=219857#p219857</ref> | |||
** 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. | |||
{| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | |||
! normal popup size | |||
! atypical size | |||
|- | |||
| {{EmbedViewer | |||
|rle = x = 35, y = 9, rule = B3/S23 | |||
b2o20bo3bo6bo$o2bo19b2ob2o6bo$o2bob3o3b2o2b3o5bobobo2b2o2bo$o2bobo2bo | |||
bo2bobo2bo4bo3bobo2bobo$o2bobo2bob4obo2bo4bo3bob4o$b2o2b3o2bo4bo2bo4b | |||
o3bobo4bo$5bo5b3o16b3o$5bo$5bo! | |||
|viewerconfig = #C [[ THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
| {{EmbedViewer | |||
|rle = x = 35, y = 9, rule = B3/S23 | |||
b2o20bo3bo6bo$o2bo19b2ob2o6bo$o2bob3o3b2o2b3o5bobobo2b2o2bo$o2bobo2bo | |||
bo2bobo2bo4bo3bobo2bobo$o2bobo2bob4obo2bo4bo3bob4o$b2o2b3o2bo4bo2bo4b | |||
o3bobo4bo$5bo5b3o16b3o$5bo$5bo! | |||
|viewerconfig = #C [[ POPUPWIDTH 480 POPUPHEIGHT 300 THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
|} | |||
* 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.<ref>https://conwaylife.com/forums/viewtopic.php?f=3&t=1622&p=135110#p135110</ref> | |||
{| class="wikitable" style="margin-left:auto; margin-right:auto; border:none" | |||
! rejects correctly | |||
! incorrectly overflows | |||
|- | |||
| {{EmbedViewer | |||
|rle = x = 7, y = 3, rule = B3/S23 | |||
bo3bo$2o3b2o$bo3bo! | |||
|viewerconfig = #C [[ X 10000000000 Y 10000000000 ZOOM 10000000000 STARTFROM 10000000000 GPS 10000000000 TILT 10000000000 DEPTH 10000000000 POITRANS 10000000000 GRAPHOPACITY 10000000000 THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
| {{EmbedViewer | |||
|rle = x = 7, y = 3, rule = B3/S23 | |||
bo3bo$2o3b2o$bo3bo! | |||
|viewerconfig = #C [[ STEP 10000000000 ANGLE 10000000000 LAYERS 10000000000 GRIDMAJOR 10000000000 HISTORYSTATES 10000000000 AGESTATES 10000000000 DELETERANGE 10000000000 THEME 10000000000 MAXGRIDSIZE 10000000000 POPUPWIDTH 10000000000 POPUPHEIGHT 10000000000 THUMBNAIL THUMBSIZE 4 WIDTH 600 HEIGHT 600 ]] | |||
}} | |||
|} | |||
== References == | |||
<references /> | |||
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) |