Pattern viewer for forum threads

[rowett]

Could the PCA icons be made to use the "just died" colour for unoccupied triangles, as to not create holes in regions where cells existed before:

...as well as made to follow the active theme (so that north = state 1 colour, east = state 2, south = state 4, west = state 8, and empty = just died colour)?

Done.

[rowett]

I also find that icons appear blurry, even at integer zoom levels, which is not the case in Golly.

Code: Select all

x = 5, y = 6, rule = Langtons-Ant
2.2A$.A.H$A3.A$A3.A$.F.A$.2A!
[[ ICONS ZOOM 32 ]]

Icons should be sharper now.

[muzik]

I also find that icons appear blurry, even at integer zoom levels, which is not the case in Golly.

Code: Select all

x = 5, y = 6, rule = Langtons-Ant
2.2A$.A.H$A3.A$A3.A$.F.A$.2A!
[[ ICONS ZOOM 32 ]]

Icons should be sharper now.

Can confirm, although they still seem fuzzy at 64x (I'd expect things to be sharper since we could just scale up the 32x icons by a factor of two).

[rowett]

Can confirm, although they still seem fuzzy at 64x (I'd expect things to be sharper since we could just scale up the 32x icons by a factor of two).

The icons use image smoothing which I prefer.

[rowett]

Cells appear to be visually offset from the grid when icons are enabled compared to when they're not.

Grid lines now line up with the icon positions.

In some cases there may be slight differences in cell positioning between the default renderer and the icon renderer.

[wirehead]

Sorry if this is documented somewhere, but I cannot, for the life of me, find the button to toggle the icons on/off. It would make sense to put it under something like the "Display" menu, but I don't know where the control for icons is. Where is it (if it even exists)?

[dvgrn]

Sorry if this is documented somewhere, but I cannot, for the life of me, find the button to toggle the icons on/off. It would make sense to put it under something like the "Display" menu, but I don't know where the control for icons is. Where is it (if it even exists)?

There's a toggle button labeled "Icon" toward the top right of LifeViewer. It's greyed out but still there if the rule doesn't have an @ICONS section, from the looks of it.

[wirehead]

Sorry if this is documented somewhere, but I cannot, for the life of me, find the button to toggle the icons on/off. It would make sense to put it under something like the "Display" menu, but I don't know where the control for icons is. Where is it (if it even exists)?

There's a toggle button labeled "Icon" toward the top right of LifeViewer.

[facepalm]

Thank you.

[b-engine]

Is there any button to toggle Sync (although Alt+S toggles it)? The button that's formerly Sync got replaced with Icon button. It would make sense if Icon button is at Display menu.

[unname4798]

Is there any button to toggle Sync (although Alt+S toggles it)? The button that's formerly Sync got replaced with Icon button. It would make sense if Icon button is at Display menu.

Settings > Clipboard > External Sync

[rowett]

... having the icons displayed in the draw menu's palette at the top right somehow would also be useful.

Done.

Sorry if this is documented somewhere, but I cannot, for the life of me, find the button to toggle the icons on/off. It would make sense to put it under something like the "Display" menu, but I don't know where the control for icons is. Where is it (if it even exists)?

There's a toggle button labeled "Icon" toward the top right of LifeViewer. It's greyed out but still there if the rule doesn't have an @ICONS section, from the looks of it.

You can also toggle Icon display with Alt+I.

Gaps also appear in cells when at non-integer zoom levels.

In Golly, icons are defined to be one row and column smaller than the cell size. For example at 32x zoom the icons are 31x31.

In LifeViewer at non-integer zooms you will get scaling artifacts.

Will it be possible to define icons for any rule via script commands, or will they be restricted to rule tables? In addition, will script commands be able to change the colours associated with existing icons?

No and no.

[muzik]

Would it be possible to make period maps for hexagonal grid oscillators use offset squares? Having highly symmetric stuff get distorted in the map is something I find irritating.

Done. Note that bounded grids will display as square but I'm not planning to fix this since bounded grids are problematic for non-square neighbourhoods anyway.

This is a massive improvement although I'm also noticing that there are gaps between the left and right edges of oscillators and the edges of the period map that wouldn't exist on square-grid period maps. Also, in the following case, the gap is bigger on the left side compared to the right side. I assume this is something that can't reasonably be solved until we figure out hexagonal selection shapes and such?

Code: Select all

x = 14, y = 3, rule = B2o4-p56/S2p34-o56H
ob4ob4obo$14o$bob4ob4obo!

Same for the following:

Code: Select all

x = 3, y = 3, rule = B3/S0H
bo$o$2bo!

I assume that using a proper hexagonal grid or triangular grid in the period map for hexagonal and triangular rules is still a backlog item?

[muzik]

For some reason, Generations rules will cause the background to be duplicated across layers, obscuring the grid and such. I don't think this should happen:

Code: Select all

x = 2, y = 4, rule = /2ae/2
o$bo$bo$o!
[[ GRID THEME Inverse LAYERS 10 HISTORYSTATES 0 AGESTATES 0 ]]

Code: Select all

x = 2, y = 4, rule = /2ae/3
o$bo$bo$o!
[[ GRID THEME Inverse LAYERS 10 HISTORYSTATES 0 AGESTATES 0 ]]

In line with the recent changes to hexagonal period maps, can we also have taller triangular period maps in the meantime that match the rectangular cell shapes?

Code: Select all

x = 4, y = 2, rule = B45/S34L
4o$o2bo!
[[ AUTOIDENTIFY ]]

Code: Select all

x = 4, y = 2, rule = R4,C2,S,B6,NL
b3o$b3o!
[[ AUTOIDENTIFY ]]

It may also be worth implementing a continuous gray border around hexagonal (offset square) period maps so that the background of the map doesn't bleed into the background of the current board as seen here.

Code: Select all

x = 3, y = 3, rule = B3/S3H
o$b2o$bo!
[[ AUTOIDENTIFY ]]

[rowett]

For some reason, Generations rules will cause the background to be duplicated across layers, obscuring the grid and such.

Fixed, thanks!

[AlbertArmStain]

Can the states in Nobili32 be recolored to match the similar rules like vonNeumann29 or Hutton32?

[muzik]

Selection/paste squares look like they might be vertically offset from the icon grid slightly - notice how (at least on my end) the top of the icons appear just on the outside when Select All is used:

Code: Select all

x = 4, y = 3, rule = Langtons-Ant
B2A$A2.A$.2AD!
[[ ICONS ZOOM 32 ]]

Is support for rotation and icon rendering planned at all?

Here's another demonstration of the case where gaps exist between the left and right on hexagonal period maps, showing it still happens when zoomed out too far for the grid:

Code: Select all

x = 58, y = 23, rule = B2o3-o4-m56/S2m3o4-o56H
b2o41b2o$o3bo38bo3bo$b4o39b4o$2bobo40bobo$3b2o41b2o14$10b2o41b2o$10bo
bo40bobo$10b4o39b4o$10bo3bo38bo3bo$12b2o41b2o!
[[ AUTOIDENTIFY ]]

For the grid button, the grid image used intersects the white boundary as well as the plus shape at the top right. This is very hard to see, but if you set the grid type to offset squares the intersection with the plus becomes much more obvious. The grid should be rendered behind the white components of buttons, but above UIBACKGROUND.

Code: Select all

x = 3, y = 3, rule = B2/SH
o$2bo$bo!
[[ COLOR GRID Black COLOR BACKGROUND #eeeeee ]]

Also, would it be possible to make the hexagonal pattern on the grid button a bit more regular to match the recent changes to the actual hexagonal grid?

[muzik]

Code: Select all

#C [[ ICONS AUTOSTART GPS 8 SHOWTIMING EXTENDEDTIMING ]]
x = 74, y = 47, rule = AnimatedPixelArt
pJuOpJuOpJuOpJuOpJuOpJuOpJuO6.pJBpJBpJBpJBpJBpJBpJB6.pJBpJBpJBpJBpJBpJ
BpJB6.pJBpJBpJBpJBpJBpJBpJB$uPuQuPuQuPuQuPuQuPuQuPuQuPuQ6.uPuQuPuQuPuQ
uPuQuPuQuPuQuPuQ6.uPBuPBuPBuPBuPBuPBuPB6.14B$pJuOKtLKtLKtLKtLKtLpJuO
6.pJBK.K.K.K.K.pJB6.pJBK.K.K.K.K.pJB6.pJBK.K.K.K.K.pJB$uPuQ10tLuPuQ6.
uPuQ10tLuPuQ6.uPBtL.tL.tL.tL.tL.uPB6.2B10.2B$pJuOKtLOtVpXvGOtVKtLpJuO
6.pJBK.O.pXCO.K.pJB6.pJBK.O.pXCO.K.pJB6.pJBK.O.pXCO.K.pJB$uPuQ2tLtTtU
vEuUtTtU2tLuPuQ6.uPuQ2tLtTtUvEuUtTtU2tLuPuQ6.uPBtL.tT.vECtT.tL.uPB6.
2B4.2C4.2B$pJuOKtLpTvGpTuUOtLKtLpJuO6.pJBK.pTCpTCO.K.pJB6.pJBK.pTCpTC
O.K.pJB6.pJBK.pTCpTCO.K.pJB$uPuQ2tLuUvF2uUtTtU2tLuPuQ6.uPuQ2tLuUvF2uU
tTtU2tLuPuQ6.uPBtL.uUCuUCtT.tL.uPB6.2B2.4C4.2B$pJuOKtLOtVpXvGOtVKtLpJ
uO6.pJBK.O.pXCO.K.pJB6.pJBK.O.pXCO.K.pJB6.pJBK.O.pXCO.K.pJB$uPuQ2tLtT
tUvEvFtTtU2tLuPuQ6.uPuQ2tLtTtUvEvFtTtU2tLuPuQ6.uPBtL.tT.vECtT.tL.uPB
6.2B4.2C4.2B$pJuOKtLOtLpTuUKtVKtLpJuO6.pJBK.O.pTCK.K.pJB6.pJBK.O.pTCK
.K.pJB6.pJBK.O.pTCK.K.pJB$uPuQ4tL2uUtTtU2tLuPuQ6.uPuQ4tL2uUtTtU2tLuPuQ
6.uPBtL.tL.uUCtT.tL.uPB6.2B4.2C4.2B$pJuOKtLpXvGpXvGpXvGKtLpJuO6.pJBK.
pXCpXCpXCK.pJB6.pJBK.pXCpXCpXCK.pJB6.pJBK.pXCpXCpXCK.pJB$uPuQ2tLvEuUvE
uUvEvF2tLuPuQ6.uPuQ2tLvEuUvEuUvEvF2tLuPuQ6.uPBtL.vECvECvECtL.uPB6.2B
2.6C2.2B$pJuOKtLKtLKtLKtLKtLpJuO6.pJBK.K.K.K.K.pJB6.pJBK.K.K.K.K.pJB
6.pJBK.K.K.K.K.pJB$uPuQ10tLuPuQ6.uPuQ10tLuPuQ6.uPBtL.tL.tL.tL.tL.uPB
6.2B10.2B$pJuOpJuOpJuOpJuOpJuOpJuOpJuO6.pJBpJBpJBpJBpJBpJBpJB6.pJBpJB
pJBpJBpJBpJBpJB6.pJBpJBpJBpJBpJBpJBpJB$uPuQuPuQuPuQuPuQuPuQuPuQuPuQ6.
uPuQuPuQuPuQuPuQuPuQuPuQuPuQ6.uPBuPBuPBuPBuPBuPBuPB6.14B4$60.KtLKtLWtX
WtXWtXKtLKtL$60.4tL6tX4tL$60.KtLWtXKtLKtLKtLWtXKtL$60.2tL2tX6tL2tX2tL
$60.KtLWtXKtLKtLKtLWtXKtL$60.2tL2tX6tL2tX2tL$27.KtLKtLWtXWtXWtXWtXWtX
WtXKtLKtL13.KtLWtXKtLKtLKtLWtXKtL$27.4tL12tX4tL13.2tL2tX6tL2tX2tL$27.
KtLWtXWtXpTuXpTuXpWuUpWuUWtXWtXKtL13.KtLKtLWtXWtXWtXKtLKtL$27.2tL4tX
8uU4tX2tL13.tM3tL6tX4tL$6.KtLKtLpIuJNtPKtL11.WtXWtXKtOWtXWtXWtXWtXNtL
WtXWtX13.LtMKtLKtLWtXKtLKtLKtL$6.3tLtVuMuJ4tL11.4tXtLtO8tXtOtL4tX13.tL
3tM2tL2tX6tL$6.KtPKtLqEvGKtLNtL11.WtXKtOWtXWtXsVyAsVyAWtXWtXNtLWtX13.
VtWWtXWtXWtXWtXWtXVtW$6.4tLvAvBtOtV2tL11.2tXtLtO4tXxWxXxWxX4tXtOtL2tX
13.4tW6tX4tW$6.pIuJqEvGKtLqEvGpIuJ11.WtXKtLWtXsVyAsVyAsVyAsVyAWtXKtLW
tX13.KtLKtLKtLWtXKtLKtLLtM$6.2uJvAvB2tLvAvB2uJ11.2tX2tO2tXxW2xXyAxXyA
xWxX2tX2tO2tX13.6tL2tX2tL2tMtLtM$6.NtLKtLqEvGKtLKtP11.WtXKtLWtXsVyAsV
yAsVyAsVyAWtXKtLWtX13.KtLKtLKtLWtXKtLKtLKtL$6.2tLtOtVvAvB4tL11.2tX2tO
2tXxW2xXyAxXyAxWxX2tX2tO2tX13.6tL2tX4tLtMtL$6.KtLNtPpIuJKtLKtL11.WtXN
tLWtXWtXsVyAsVyAWtXWtXKtOWtX13.KtLKtLKtLWtXKtLKtLKtL$6.4tLuMuJtLtV2tL
11.2tXtOtL4tXxWxXxWxX4tXtLtO2tX13.6tL2tX6tL$27.WtXWtXNtLWtXWtXWtXWtXK
tOWtXWtX13.KtLKtLWtXKtLWtXKtLKtL$27.4tXtOtL8tXtLtO4tX13.4tL2tX2tL2tX
4tL$27.KtLWtXWtXpWuUpWuUpTuXpTuXWtXWtXKtL13.KtLWtXKtLKtLKtLWtXKtL$27.
2tL4tX8uU4tX2tL13.2tL2tW2tM2tL2tM2tW2tL$27.KtLKtLWtXWtXWtXWtXWtXWtXKtL
KtL13.VtWLtMKtLKtLKtLLtMVtW$27.4tL12tX4tL13.2tWtL2tM3tLtM2tLtM2tW!

This now seems far laggier than it previously was when icons were first implemented, but I'll need to check this on other devices as well.

[rowett]

This now seems far laggier than it previously was when icons were first implemented, but I'll need to check this on other devices as well.

Yes I switched image scaling to "high". It didn't have much impact on my desktop but has certainly had a dramatic performance hit on mobile.

I'm currently working on a new renderer. I'll see if it's any better.

EDIT: The new renderer is deployed in build 1162:

• Improved performance on mobile
• Preservation of blank right column and bottom row
• More accurate use of different icon sizes specified
• Remove Icon display for Zooms < 8x

Can the states in Nobili32 be recolored to match the similar rules like vonNeumann29 or Hutton32?

It would need to be done on the LifeWiki rule repository.

Is support for rotation and icon rendering planned at all?

No.

[muzik]

I am not sure if Identify should report this as FlipX, as this transformation is atypical for diagonal spaceships.

Code: Select all

x = 8, y = 10, rule = R3,C2,S5-7,B5-7,NW0000000202020000000002010200000000020202000000000
6o$6o$2o4b2o$2o4b2o$2o$2o$2o$2o$2b2o2b2o$2b2o2b2o!

Similar for this diagonal flipping camelship:

Code: Select all

x = 6, y = 6, rule = R3,C2,S5-7,B5-7,NW0000000002020200000000020102000000000202020000000
6o$6o$2o$2o$2b2o$2b2o!

and this "FlipY" camelship:

Code: Select all

x = 20, y = 16, rule = R5,C2,S5-7,B5-7,NW0000000000000000000000002000200020000000000000000000000000000000000020001000200000000000000000000000000000000000200020002
4b4o$4b4o$4b4o$4b4o$4o$4o$4o$4o$4o12b4o$4o12b4o$4o12b4o$4o12b4o$16o$16o
$16o$16o!

This orthogonal spaceship is reported as having a mod equal to its period, which I think is correct:

Code: Select all

x = 12, y = 12, rule = R5,C2,S5-7,B5-7,NW0000000000000000000000002000200020000000000000000000000000000000000020001000200000000000000000000000000000000000200020002
4b4o$4b4o$4b4o$4b4o$4o$4o$4o$4o$12o$12o$12o$12o!

Easy fix for some of these would be to immediately rule out any mod transforms for oblique spaceships, though weird results for orthogonal and diagonal spaceships may require more work.

I assume that the Golly icon set for [R]History and [R]Super will not be implemented into LifeViewer in line with this post?

Also is it possible to display a "code box" on the wiki, the same way as on the forum?

[rowett]

I assume that the Golly icon set for [R]History and [R]Super will not be implemented into LifeViewer in line with this post?

Correct.

Also is it possible to display a "code box" on the wiki, the same way as on the forum?

I don't know. The code boxes on the forum are generated by the forum software. I presume something similar might be possible on the Wiki. In either case it's not a LifeViewer question.

[muzik]

This pattern has AGESTATES set to 1 so that there are only two colors for living cells: freshly born and having survived. Why, then, does the height increase gradually with playback? Shouldn't maximum height be reached immediately at T=1 due to the surviving cells reaching their max age at this specific generation?

Code: Select all

x = 12, y = 7, rule = B3/S23
3bo$3bo$2b3o5bo$7o2bobo$2b3o5bo$3bo$3bo!
[[ AGESTATES 1 HISTORYSTATES 1 LAYERS 10 GRID ]]

Also, for custom rules, how exactly does the fast lookup table specification work, and is there any way that these tables can be saved, perhaps such that they could be added to the LifeWiki's rule pages so that LifeViewer can pull from there directly without having to generate it from an existing table or tree?

[unname4798]

This pattern has AGESTATES set to 1 so that there are only two colors for living cells: freshly born and having survived. Why, then, does the height increase gradually with playback? Shouldn't maximum height be reached immediately at T=1 due to the surviving cells reaching their max age at this specific generation?

Code: Select all

x = 12, y = 7, rule = B3/S23
3bo$3bo$2b3o5bo$7o2bobo$2b3o5bo$3bo$3bo!
[[ AGESTATES 1 HISTORYSTATES 1 LAYERS 10 GRID ]]

Also, for custom rules, 1) how exactly does the fast lookup table specification work, and 2) is there any way that these tables can be saved, perhaps such that they could be added to the LifeWiki's rule pages so that LifeViewer can pull from there directly without having to generate it from an existing table or tree?

2) No, LifeViewer doesn't support user-defined fast lookup tables.

[rowett]

This pattern has AGESTATES set to 1 so that there are only two colors for living cells: freshly born and having survived. Why, then, does the height increase gradually with playback?

Because it looks nicer seeing the towers grow. You get the age information from the cell colour.

Also, for custom rules, how exactly does the fast lookup table specification work, and is there any way that these tables can be saved, perhaps such that they could be added to the LifeWiki's rule pages so that LifeViewer can pull from there directly without having to generate it from an existing table or tree?

The fast lookup feature builds an in-memory lookup table for RuleLoader rules with a small enough combination of states and neighbours. If the lookup table is small then it's not worth saving since it's quick to generate. If the lookup table is big then it's too large to save.

[muzik]

Hexagonal Selections

Can anyone point me at a tool or paper that describes a good way of making selections on a hexagonal grid?

Asked around on Reddit since I've still been thinking about this for a while. Here's a demo for generating a hexagonal boundary given two points - would it be sufficient for LifeViewer, or not?

https://www.desmos.com/calculator/tq2beqznnk

[muzik]

The "Icon" button will become permanently enabled instead of grayed out if you enter a rule with a valid icon set, then one that doesn't.

Code: Select all

x = 5, y = 5, rule = B3/S23
3b2o$2b3o$bob2o$bo$o!

Code: Select all

x = 5, y = 5, rule = Pulse2
3b2o$2b3o$bob2o$bo$o!

Also noticing that the width for the period map key is now a constant width where it would previously adjust to fit however wide the biggest number was. This can cause it to intersect the map itself a lot more easily. I assume this resulted from the change that permitted the map key to take up two columns:

Code: Select all

x = 54, y = 1, rule = MAPAAD//zAwPz8AAP//MDA/PwAA//8AAP//AAD//wAA//8AAD8/AAD//wAAPz8AAP//wMD//wAA///AwP//AAD//w
54o!
[[ AUTOIDENTIFY COLOR UIBACKGROUND DeepSkyBlue ]]

Code: Select all

x = 156, y = 75, rule = B3/S23
146b2o5b2o$146b2o5b2o16$145b2obo3bob2o$145bo2bo3bo2bo$146b3o3b3o3$31b
2o$33bo$18b2o10b2o2bo$18b2o11bo2bo$32bobo$32b2o119b2o$153b2o$32b2o$32b
obo$18b2o11bo2bo10b2o30b2o$18b2o10b2o2bo10b2o30b2o$b2o4b3o23bo$b2o3bo
3bo20b2o$6b2ob2o$7bobo67bo$53bo2bo19bobo66bo2bo$7bobo21b4o22bo17b2ob2o
69bo$6b2ob2o19bo3bo18bo3bo16bobob3o64bo3bo$6bo3bo4b2o17bo19b4o14bob2o
2b2o66b4o$7b3o4b2o14bo2bo38bobo77b2o$16bo135bobo$154bo$86b2o34bo31b2o
$69b2o15bobo7b2o24b2o$51bo3b3o11b2o17bo7b2o23bobo$36b2o12bobo2b5o26b3o
$36b2o12bo3b2o3b2o$51bo2bo3b2o$3o5b3o41b3o3bo$o2b2ob2o2bo16bo58b3o$b3o
3b3o16b2o24b3o3bo10b2o17bo7b2o$2bo5bo17bobo22bo2bo3b2o9b2o15bobo7b2o$
36b2o12bo3b2o3b2o2b2o21b2o$36b2o12bobo2b5o3b2o$51bo3b3o52b2o$111b2o$92b
o17bo$50b2o38bo2bo$b2o5b2o42bo25b2o10b5o$b2o5b2o39b2o2bo10b2o12b2o10b
3ob2o$31bo18bo2bo10b2o25b2obo15bo3bo$30bo2bo4b2o11bobo38b2o15bo5bo9b2o
$17b2o10b5o3b2o12b2o56bo15b2o$17b2o9b2ob3o5bo52b2o15b2o3bo$29bob2o18b
2o38b2obo16b3o$30b2o19bobo24b2o10b3ob2o$50bo2bo10b2o12b2o10b5o16b3o$30b
2o17b2o2bo10b2o24bo2bo15b2o3bo$29bob2o19bo39bo16bo15b2o$17b2o9b2ob3o16b
2o57bo5bo9b2o$17b2o10b5o76bo3bo$30bo2bo$31bo!
[[ AUTOIDENTIFY COLOR UIBACKGROUND DeepSkyBlue ]]

Code: Select all

x = 154, y = 142, rule = B3/S23
84b2o9b2o48b2o$83bo2bo9bo48bo$84b3o9bobo44bobo$83bo3bo9b2o9b2o22b3o8b
2o$82bob4o18b2o2bo19bo3b2o$69b2o11bobob2o18bo2b3o2b2o10b2o2bobo2b2o$70b
o12bobobobo16bo4bo2b2o10b2obo5bo$70bobo12b2obobo16b5o18b5o$71b2o3bo8b
4obo$77b2o6bo3bo17b5o18b5o$77b2o7b3o17bo4bo2b2o10b2obo5bo$66b2o5bo3bo
3bo4bo2bo16bo2b3o2b2o10b2o2bobo2b2o$71bobo3bo3b3o3b2o17b2o2bo19bo3b2o
$65bo3bo6b2o3b3o13b2o9b2o22b3o8b2o$64bo4bo6b2o4b3o11bobo44bobo$63bobo
bo5b3o4b2o14bo48bo$62bobobo7b3o3b2o13b2o48b2o$56b2o2bo4bo8b3o3bo3bobo
$56b2o2bo3bo11bo3bo3bo$70bo2bo5b2o36b2o6b2o$52bo9b2o6bo8b2o35bo2bo4bo
2bo$51bobo15bo4bo6bo3b2o29bo2bo4bo2bo$52bo15bobo2b2o10bobo28bo2bo4bo2b
o$56b3obo5b2obo17bo29b2o6b2o$55bob2ob2o25b3o7b2o$55bo5b2o27bo6bo$55b2o
5bo3bo2bo19b2o4bobo15b2o16b2o$56b2ob2obo5b2o25b2o17bo16bo$57bob3o29b3o
12b2o6bob2o10b2obo$65bo25b3o11bo2bo6bo3bo6bo3bo$64bobo38bobobo10bo4bo
$65bo3bo18b2o16bo2bo6bo3bo4bo3bo$68bobo16bobo4b2o14bo9bo4bo$60b2o6bob
o16bo6bo12bobo5bo3bo6bo3bo$60b2o4b3o2b2o13b2o7b3o16bob2o10b2obo$65b2o
2bobo8bo16bo16bo16bo$64bobob2o2bo6bobo15bob2o10b2obo16b2o$62b3obo3b2o
3bo13b2o7bo3bo6bo3bo38b2o$54b2o5bo4bob2o5bo2bo2bo4b2o2bo12bo4bo26bobo
2b2o6b3o2bo$54bobo4b2o3b2obo4bob2o7b2ob2o9bo3bo4bo3bo21bo2bo2bobo8b2o
$56bo2b2o17b2o5b2o16bo4bo9b2o15b2obo3bo4bo$47b2o6b2obobo14b2o2bo5b2o11b
o3bo6bo3bo4b2o19b2ob2o3bo$47b2o9bo16b2o3b2o3b2ob2o7bob2o10b2obo24b2o2b
o7b2o$54b5o2bo15bo8b2o2bo6bo16bo10b5o5b3o3b3o4b3o2bo$55bo3b3o17b3o7b2o
5b2o16b2o9bo9bo2b2o12b2o$54b2ob2o67bo2bo5b2ob2o$53bo5bo67b2o7bo3bob2o
$53b6o47b2o16b2o10bobo2bo2bo$98bo6bobo3b2o10bo2bo10b2o2bobo$55b2o22b3o
16b2o4bo2bo3b2o14bo$55b2o12bo12bo4b3o12bo3bo16b5o$69b2o7bo3bo3bo3bo11b
obo$47b3o27bobo2bo2bo5bo41b2o$46bo3bo14bobo2b3o2bo2bobo21bobo28b2o$45b
o5bo13b4obo4bo3bo4bo7bo9bo3bo$46bo3bo14b2o8bo8bo7bo5b2o4bo2bo3b2o$36b
3o8b3o26b3o19bo6bobo3b2o$18b2o5b2o9b3o8b3o35bo5bo14b2o$18b2o5b2o9b3o47b
o3bo29b2o15b2o$18b2o5b2o6b3o51b3o30b2o15b2o$18bo7bo6b3o39b2o$16b2ob2o
3b2ob2o4b3o11b2o25bo2bo$16b2ob2o3b2ob2o18b2o25bobobo$16b2o2bo3bo2b2o46b
ob3o53b2o$7b2o8b2obo3bob2o49b3o15bo2b2o4b2o2bo24bobo$7bo2b3o5b2o5b2o67b
o3b3o2b3o3bo18b3o$8b2o9bo5bo9b2o58bo2b2o4b2o2bo18bo3bo$13bo20b4o36b2o
50b2o3b2o$13bo19bo2bobo33bo4bo49bo$8b2o22bobo2b2o32bo6bo22b2o25b5o$7b
o2b3o5b2o5b2o4bobo36bo8bo3b3o43bo$7b2o9b2o5b2o3b2o38bo8bo5bo17bo5bo$18b
2o5b2o3b3o37bo8bo4bo18bo5bo3bo$18bo7bo4bobo37bo6bo22b4o3b4o17bo$16b2o
b2o3b2ob2o3b2o38bo4bo22b2o9b2o13b5o$16b2ob2o3b2ob2o45b2o23b3o2b2ob2o2b
3o17bo$5bobo8b2o2bo3bo2b2o70b2o3b2ob2o3b2o12b2o3b2o$4bo2bo9b2obo3bob2o
42bo2bo26b3obo3bob3o14bo3bo$4b2o2b2o8b2o5b2o47bo26b2o7b2o16b3o$4bo4bo
9bo5bo7b2o34bo5bo26b3o3b3o12bobo$b3o5bo22bo2bo33b2o4bo28b2ob2o15b2o$o
bo5bo22bobobo38bo28bobobobo$7bo23bo2bo38bo21b2o7bo3bo$2o4bobo9b2o5b2o
3bo41b4obo17b2o$2bo2bobobo2b2o4b2o5b2o4bobo38bo3bo43b2o15b2o$2b3o3bo3b
2o56bo3bo21bo23b2o15b2o$34b2o33bob4o20bobo$32bo4bo35bo16b2o2bo2bo4b3o
3b3o$8b2o21bo6bo33bo17b2obo8b2obobob2o$8b2o20bo8bo3b3o25bo4b2o16b2o9b
obo$30bo8bo5bo25bo5bo$30bo8bo4bo27bo31b2ob2o$31bo6bo34bo2bo6bo4bo$32b
o4bo43b3o3bob2o$34b2o44bo6bobo5b2o$80b2o6bobo3bobo$93b3o$74bob2o15b2o
$73bo2bob2o14bobo$73bo2bo3bo14bobo2b2o$73b3o20bo2bobo$68bo11bo16b4o$67b
o11bo18b2o$72b3o$67bo3bo2bo$68b2obo2bo$70b2obo$49bo$49b3o14b2o$52bo14b
o$51b2o11b3o$64bo$62bobo$62b2o7$58bobo$57bo2bo$57bo2bo$58bo2$53bo$51b
o2bo$51bo2bo$51bobo7$48b2o$47bobo$47bo$46b2o11b2o$59bo$60b3o$62bo!
[[ AUTOIDENTIFY COLOR UIBACKGROUND DeepSkyBlue ]]

Something I've noticed that's most likely low priority to fix since I'm yet to reproduce this without paste commands: I'd expect a diagonal flip transform to be reported here with Identify since it does indeed flip diagonally in the same way some spaceships like gliders would when travelling, but Identify doesn't produce this in the output.

Code: Select all

x = 1, y = 1, rule = B/S
!
[[
PASTET EVERY 2 0 PASTEDELTA 2 2 PASTE bo$b3o$3o$2bo! 0 0
PASTET EVERY 2 1 PASTEDELTA 2 2 PASTE 2bo$3o$b3o$bo! 1 1
]]

Code: Select all

x = 1, y = 1, rule = B/S5n
!
[[
PASTET EVERY 4 0 PASTEDELTA 2 2 PASTE bo$b3o$3o$2bo! 0 0
PASTET EVERY 4 2 PASTEDELTA 2 2 PASTE 2bo$3o$b3o$bo! 1 1
]]

Code: Select all

x = 1, y = 1, rule = B/S2a
!
[[
PASTET EVERY 4 0 PASTEDELTA 2 2 PASTE bo$b3o$3o$2bo! 0 0
PASTET EVERY 4 2 PASTEDELTA 2 2 PASTE 2bo$3o$b3o$bo! 1 1
]]

For multistate higher-range rules there is no prompt stating that cells were deleted at the boundary, probably due to it simply suppressing births in this case - I do not know if this is how it's meant to work in this rulespace or not:

Code: Select all

x = 2, y = 4, rule = /2/2
o$bo$bo$o!
[[ MAXGRIDSIZE 9 STARTFROM 253 X 256 ]]

Code: Select all

x = 2, y = 4, rule = R1,C2,S,B2
o$bo$bo$o!
[[ MAXGRIDSIZE 9 STARTFROM 253 X 256 ]]

Code: Select all

x = 2, y = 4, rule = /2/3
A$BA$BA$A!
[[ MAXGRIDSIZE 9 STARTFROM 253 X 256 ]]

Code: Select all

x = 2, y = 4, rule = R1,C3,S,B2
A$BA$BA$A!
[[ MAXGRIDSIZE 9 STARTFROM 253 X 256 ]]

This pattern has four permanently alive cells after everything else dies, which seems quite wrong to me:

Code: Select all

x = 2, y = 2, rule = R1,C3,S,B2
2A$2A!
[[ MAXGRIDSIZE 9 STARTFROM 509 ZOOM -1 ]]

What's planned next for LifeViewer in terms of features and supported rulespaces?