Pattern viewer for forum threads

[rowett]

Some suggestions relating to bounded grids

I'll put them on the backlog but it's not high priority for me.

Can B0 Generations be permitted on bounded grids, since LtL/HROT-with-decay can be?

No. I don't like the LtL/HROT B0 flashing but Golly supports it so for compatibility so did LifeViewer.

[rowett]

Also can PCA cells with more subcells inside of them be taller in Layers if they aren't already

Probably not but I'll put it on the backlog.

Will support for changing their colour via specifying their cell type e.g. NSW instead of their state number be supported at all?

Yes, done.

... could we have some sort of way to select which states can be present in a random fill and which ones cannot?

At the moment there are just two choices: all states, or just the alive and dead states. If you can think of a nice way to select up to 256 states to include please let me know.

[muzik]

... could we have some sort of way to select which states can be present in a random fill and which ones cannot?

At the moment there are just two choices: all states, or just the alive and dead states. If you can think of a nice way to select up to 256 states to include please let me know.

Something like the interface used to select the state to draw with, except multiple can be selected and these would be the used states.

[muzik]

It seems that LifeViewer's/the forum's way of dealing with invalid patterns now is to not display the show in viewer option, as opposed to it previously being possible to open them but with an error being displayed.

So far this is the only remaining example of the old behaviour:

Code: Select all

 x = 1, y = 1, rule = B3/S23
8193o!

It probably shouldn't display the option for such patterns.

Also could the in-viewer change rule function be made to reject invalid rules instead of accepting them then showing the error?

[muzik]

Could themes also be allowed to hold colour info for UI elements, so that for example the Blues theme causes lifeviewer to roughly display like it did pre-2019?

Code: Select all

 x = 4, y = 7, rule = B3/S23
o$o$o$o$b2o$3bo$3bo!
[[ COLOR UIBORDER 0 255 255 ]]

An example theme for Generations:

Code: Select all

 x = 4, y = 7, rule = B3/S23
o$o$o$o$b2o$3bo$3bo!
[[ THEME Generations COLOR UISELECT 192 0 0 COLOR UIBORDER 255 255 0 COLOR UIHIGHLIGHT 255 128 0 ]]

and for the fire theme:

Code: Select all

 x = 4, y = 7, rule = B3/S23
o$o$o$o$b2o$3bo$3bo!
[[ THEME Fire COLOR UISELECT 160 0 0 COLOR UIBORDER 255 144 0 COLOR UIHIGHLIGHT 255 125 0 ]]

Can provide more if desired.

If these are implemented it might be fitting for the theme selection menu to have each individual button formatted to the theme it represents.

----

Named PCA states don't seem to be listed in Help > Scripts > Colours even though the changelog says their names are implemented.

There's also this one more alias:
https://gitlab.com/apgoucher/catagolue/ ... 8851a05d36

ElectrumLife is also missing a slash

[rowett]

Could themes also be allowed to hold colour info for UI elements, so that for example the Blues theme causes lifeviewer to roughly display like it did pre-2019?

I'll put it on the backlog though I think there should be options to change the Theme without changing the UI colours and vice verse.

Can provide more if desired.

Yes we'll need them for each existing Theme if it's going to be implemented.

Named PCA states don't seem to be listed in Help > Scripts > Colours even though the changelog says their names are implemented.

There's also this one more alias:
https://gitlab.com/apgoucher/catagolue/ ... 8851a05d36

ElectrumLife is also missing a slash

All done, thanks.

[Macbi]

Feature request: With the introduction of 'show in LifeViewer' for Golly, it would also be nice to have 'show in Golly' in LifeViewer. You would be able to do it by just having a 'Download RLE' button, since users could then tell their browser to open downloaded .rles in Golly.

[muzik]

https://lazyslug.com/lifeview/plugin/triangular.html

Go to the history demonstration on this page and try drawing with the states lifehistory adds.

[GUYTU6J]

When playing with Hdj's hexagonal rule:

Code: Select all

x = 12, y = 12, rule = B2o/S2oH
2o$obo$o2bo2$2b2o$3bo$bo3$10b2o$8bo2bo$10b2o!

I select and random-fill a region covering the oscillator repeatedly while running. After several rounds, some strange non-interacting cells started blinking at p2, that is, they die out and reborn quickly. Running the pattern at step 1 by clicking buttons display the effect clearly. But if I random-fill somewhere else not covering the blinking cells, they die out.

[rowett]

... it would also be nice to have 'show in Golly' in LifeViewer. You would be able to do it by just having a 'Download RLE' button, since users could then tell their browser to open downloaded .rles in Golly.

This would be too awkward plus my browser won't open rle files in Golly. Just use copy Ctrl-C and then paste or open clipboard in Golly.

[rowett]

https://lazyslug.com/lifeview/plugin/triangular.html

Go to the history demonstration on this page and try drawing with the states lifehistory adds.

Fixed in the next released. Thanks for reporting!

[rowett]

After several rounds, some strange non-interacting cells started blinking at p2

This has been fixed and will be in the next release. Thanks for reporting!

[muzik]

Can the boundary cells of bounded grids be able to be customized? This command only appears to affect the outside of non-bounded grids. If added, they should probably be independently configurable.

Code: Select all

 x = 33, y = 27, rule = LifeHistory:P64,32
13.F3$10.F4$2C5.2A3D$2C5.2A2.D$11.D$4.2A3.2D$4.2A5$22.2E.2A$21.E5.A$
21.E6.A2.2C$21.3E3.A3.2C$26.A3$22.F3$19.F!
[[ THEME Blues COLOR BOUNDARY 127 0 255 ]]

Also I'm not sure why the grid appears outside of the border.

Will markoff cells be able to support the fading effect that dead cells do?

[rowett]

Can the boundary cells of bounded grids be able to be customized?

Yes.

Also I'm not sure why the grid appears outside of the border.

It makes the rendering faster.

Will markoff cells be able to support the fading effect that dead cells do?

No.

[muzik]

Try running identify on this:

Code: Select all

 x = 44, y = 48, rule = plife
40b2o$40bob2o$41bobo$40bo2bo$40b3o6$22b2o$22bob2o$23bobo$22bo2bo$22b3o
10$33b3o$36b3o$34bo4bo$8b2o29bo$8bob2o23bo2bo$9bobo24bo$8bo2bo$8b3o4$
26bo$27bo$26bo2$22b2o$21bo2bo$22b2o2$2bo$bobo$2o$bo$o!

A random thought, could functionality to LifeViewer be added for 2-state ruletables that convers the rule table into the corresponding isotropic non-totalistic rule where applicable in Hensel notation? Like with the following script: viewtopic.php?f=9&t=1480&p=26017#p27013

[rowett]

Try running identify on this

All good now, thanks for the report!

[rowett]

could functionality to LifeViewer be added for 2-state ruletables that convers the rule table into the corresponding isotropic non-totalistic rule where applicable in Hensel notation?

What's the benefit?

[muzik]

could functionality to LifeViewer be added for 2-state ruletables that convers the rule table into the corresponding isotropic non-totalistic rule where applicable in Hensel notation?

What's the benefit?

Mainly for faster identification of named 2-state isotropic rules which have ruletables but the actual hensel notation is not provided, so I can get the rulestrings right on the spot and commit them to catagolue (and then be added to the LV alias list) instead of having to manually install each rule on Golly and run the script to find them out (which isn't possible for me when away from home).

[muzik]

Almost certaintly known but identify doesn't work properly for hex or tri patterns due to it only considering a square grid:

Code: Select all

 x = 4, y = 3, rule = B2o/S2oH
2b2o$o2bo$2b2o!

should be p6 but mod 1.

(Can the identify table be made to have borders like other interface items do? It's kinda hard to see where it ends on most themes.)

Also, can hex patterns be corrected to show centered when first loaded, instead of displaying the region they would take up on a normal square grid?

Code: Select all

 x = 65, y = 64, rule = bs0123456h
o$2o$obo$4o$o3bo$2o2b2o$obobobo$8o$o7bo$2o6b2o$obo5bobo$4o4b4o$o3bo3bo
3bo$2o2b2o2b2o2b2o$obobobobobobobo$16o$o15bo$2o14b2o$obo13bobo$4o12b4o
$o3bo11bo3bo$2o2b2o10b2o2b2o$obobobo9bobobobo$8o8b8o$o7bo7bo7bo$2o6b2o
6b2o6b2o$obo5bobo5bobo5bobo$4o4b4o4b4o4b4o$o3bo3bo3bo3bo3bo3bo3bo$2o2b
2o2b2o2b2o2b2o2b2o2b2o2b2o$obobobobobobobobobobobobobobobo$32o$o31bo$
2o30b2o$obo29bobo$4o28b4o$o3bo27bo3bo$2o2b2o26b2o2b2o$obobobo25bobobob
o$8o24b8o$o7bo23bo7bo$2o6b2o22b2o6b2o$obo5bobo21bobo5bobo$4o4b4o20b4o
4b4o$o3bo3bo3bo19bo3bo3bo3bo$2o2b2o2b2o2b2o18b2o2b2o2b2o2b2o$obobobobo
bobobo17bobobobobobobobo$16o16b16o$o15bo15bo15bo$2o14b2o14b2o14b2o$obo
13bobo13bobo13bobo$4o12b4o12b4o12b4o$o3bo11bo3bo11bo3bo11bo3bo$2o2b2o
10b2o2b2o10b2o2b2o10b2o2b2o$obobobo9bobobobo9bobobobo9bobobobo$8o8b8o
8b8o8b8o$o7bo7bo7bo7bo7bo7bo7bo$2o6b2o6b2o6b2o6b2o6b2o6b2o6b2o$obo5bob
o5bobo5bobo5bobo5bobo5bobo5bobo$4o4b4o4b4o4b4o4b4o4b4o4b4o4b4o$o3bo3bo
3bo3bo3bo3bo3bo3bo3bo3bo3bo3bo3bo3bo3bo$2o2b2o2b2o2b2o2b2o2b2o2b2o2b2o
2b2o2b2o2b2o2b2o2b2o2b2o2b2o2b2o$obobobobobobobobobobobobobobobobobobo
bobobobobobobobobobobobobo$64o!

[rowett]

Almost certaintly known but identify doesn't work properly for hex or tri patterns due to it only considering a square grid

True. I'll hide the Mod value.

(Can the identify table be made to have borders like other interface items do? It's kinda hard to see where it ends on most themes.)

No I think it looks worse with the box.

Also, can hex patterns be corrected to show centered when first loaded, instead of displaying the region they would take up on a normal square grid?

Yes this has been on the backlog a while I'll take a look.

[GUYTU6J]

I'm unable to use the select tool in the torus with a zero dimension.

Code: Select all

x = 70, y = 24, rule = B3/S23:T0,24
68b2o$68b2o$61b2o6bo$56b2o5b2obo2bo$3b2ob4o48b2o3b2o3b2o$2obo4b2o7b2o
9bo22bo6b2ob2o5b2o$3bo5bo8bo8bobo10bo9bo2bo2b2o11bo$ob2o4bo5b2ob2o10b
2o4bo3b2o6bo5b2o14bo$bo6bo6bobo10b2o5bo2b3o6bo3bo4b2o3b2o5b2o$16bo13bo
4bo3b2obo4bo10b2o3b2o3b2o$28bob3o7b3o15b2o3b2obo2bo$2o18bobo4bobo3bo7b
o14b2o3b2o6bo$3o11bo5bobo4b2obo2bo34b2o$b2o9b2o5bo3bo3bo5bo34b2o$13b2o
3b3o7bo3bo36bo$2bo13bo2b5o7bo37bo$7bo7b2o2bo9b2o37b2o$16bobo49b2o$8bo
8bo51bo$69bo$68b2o$68b2o$69bo$69bo!

[rowett]

I'm unable to use the select tool in the torus with a zero dimension.

It should be fixed now - thanks for reporting!

[muzik]

Might be prudent to also remove the direction and slope parameter for spaceships, since they don't work consistently either:

Code: Select all

 x = 5, y = 5, rule = B2/S2H
o2b2o$3b2o$2bo2$4bo!

Code: Select all

 x = 5, y = 5, rule = B2/S2H
obobo2$3bo$3b2o$4bo!

Will mod be able to work properly for hex/tri oscillators in the future? Also, how would one even notate coordinates on a p6 symmetric grid without just mapping it to a square grid and losing symmetry? Orthogonal and diagonal ships are defined, but all other displacements haven't been to my knowledge, so notating their displacements on a hex grid seems like a big challenge.

[rowett]

Might be prudent to also remove the direction and slope parameter for spaceships

Done.

Will mod be able to work properly for hex/tri oscillators in the future?

Perhaps as part of a bigger piece of work to improve handling of non-square grids in general. For example hexagonal or triangular selections in the editor. It's on the backlog but low priority.

[muzik]

Actually it might be possible to return the direction parameter if these directions:

Code: Select all

x = 15, y = 15, rule = B24/S02H
bo3b2o$o7bo$ob2o2b2o$2bo5bo2$12bo$obo8bobo$2bo9bo$bobo8bobo$2bo2$6bo5b
o$7b2o2b2obo$6bo7bo$8b2o3bo!

(1,0), (1,1), (0,-1), (-1,0), (-1,-1), (0,1)
are reported as orthogonal, these directions:

Code: Select all

 x = 23, y = 23, rule = B2/S2H
4bo$4b2o$5bo2$4bobobo2bo2b2o$14b2o$13bo$2o2bo$b2o12bo$4bo2$4bo13bo2$
18bo$7bo12b2o$18bo2b2o$9bo$7b2o$7b2o2bo2bobobo2$17bo$17b2o$18bo!

(1,-1), (2,1), (1,2), (-1,1), (-2,-1), (-1,-2)
as diagonal, and any other direction as generically oblique.


Is it intended that when a lifeviewer window is moved and then closed, and a new one is opened, it appears in the old viewer's spot? This gets kind of annoying as sometimes reopening safari ends up placing it at the left and I need to manually move it back to the right again.

There are also script errors on this page and patterns seem to be tracked along the wrong direction: http://lazyslug.com/lifeview/plugin/trackbox.html

And this doesn't seem to have a settings button, at least not on safari:

Code: Select all

x = 15, y = 8, rule = B3-y5cr/S234w6n
3b2o2b2o3b2o$3b2o2b2o3b2o4$2o2b2o$2obo2bo2b2o2b2o$4b2o3b2o2b2o!
[[ POPUPWIDTH 1300 ]]