Pattern viewer for forum threads

[muzik]

I've also been experiencing frequent crashing/freezing on iOS with hexagonal and triangular patterns, but don't know exactly why.

I can't reproduce this.

I have a test case set up here: viewtopic.php?f=11&p=158227#p158227

This no longer seems to happen.

[muzik]

This seems to crash consistently at T 774:

Code: Select all

x = 2, y = 2, rule = R1,C2,S0,2,4,6,8,B1,3,5,7,NM
2o$2o!
[[ AUTOSTART MAXGRIDSIZE 9 DELETERANGE 1 ZOOM -1 ]]

What is it that causes this to become asymmetric anyway, whereas the range-1 algorithm doesn't?

[muzik]

In Help > Info > Pattern, if the RLE specifies the dimensions of a pattern to be 0, said values are converted to 1, even though the RLE did not specify 1. Is this intended behaviour?

Code: Select all

x = 6, y = 0, rule = B/S
!

Code: Select all

x = 0, y = 0, rule = B/S
!

Code: Select all

x = -7, y = -7, rule = B/S
!

Code: Select all

x = -0, y = -7, rule = B/S
!

I'm also curious as to whether it's technically correct for an RLE with no pattern data preceding the ! to be classified as 1x1: it contains no cells, so 0x0 seems more fitting in this case (if it instead specified one empty cell via a single b, that would count as 1x1).

A minor thing to point out: the capitalisation of messages displayed by certain actions isn't consistent: for example, "Pattern Saved" capitalizes every word, but "New pattern" does not. Not sure if it's at all worth unifying the formatting of all such messages.

Given that the last update to LifeViewer was a month and a half ago I assume a break is being taken from all LifeViewer-related activities?

[b3s23love]

Select appears to be offset for MAP rules on a torus. What is even more bizarre is that the bug only arises when using a MAP rule and only on a torus. In that conditions the Select set of features (Select All, Copy and Paste) is also broken.

Code: Select all

x = 200, y = 200, rule = Movingstrings:T200,200
90$6bobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobo
bobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobobo
bobobobobobobobobobobobobobo$4b167o$ob3o165b3obobobobobobobobobobobobo
bo$3o169b28o!

[muzik]

Identify on bounded grids now returns the bounding box of the oscillator rather than the size of the bounded grid like it did before.

Code: Select all

x = 3, y = 1, rule = B3/S23:P21,21
3o!

Help > Info > Identify also displays a value for "Back" even if no background cells are present in the period map.

Code: Select all

x = 2, y = 4, rule = B3/S23:T2,4
2$2o$2o!

Also, if we blank out the contents of the text box over at https://lazyslug.com/lifeview/plugin/viewer.html and press View, we still don't get a "New pattern" message despite the fact that doing this loads an empty pattern.

We don't get a new pattern message either if all of the non-zero cells in a pattern are placed outside of a bounding box:

Code: Select all

x = 1, y = 1, rule = B3/S23:T10,10
20bo!

I've also noticed that downloaded period maps don't use the expected colors, resulting in minor artifacts. If you use the in-viewer button to download the period map for this after identifying it, then open up the file in mspaint and use the fill option to fill in some regions, you'll probably encounter a few pixels of slightly differing colors that didn't get filled in. What exactly is causing this, and is it fixable?

Code: Select all

x = 8, y = 6, rule = B3/S23
2bo$o3b4o$o3bo$o$3bo$b2o!

Finally, an inconsistency: most bounded grid types do not accept negative zero as a size, even though they accept normal zero. Toruses accept it just fine:

Code: Select all

x = 5, y = 4, rule = B3/S23:T0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:T-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:T0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:T0,-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:T-0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:T-0,-0
bo2bo$o$o3bo$4o!

Planes do not:

Code: Select all

x = 5, y = 4, rule = B3/S23:P0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:P-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:P0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:P0,-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:P-0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:P-0,-0
bo2bo$o$o3bo$4o!

Neither do cross-surfaces:

Code: Select all

x = 5, y = 4, rule = B3/S23:C0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:C-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:C0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:C0,-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:C-0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:C-0,-0
bo2bo$o$o3bo$4o!

Klein bottles work fine if no twist is specified:

Code: Select all

x = 5, y = 4, rule = B3/S23:K0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K0,-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0,-0
bo2bo$o$o3bo$4o!

It gets more hit and miss if we specify a twist, though:

Code: Select all

x = 5, y = 4, rule = B3/S23:K0*
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0*
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K0*,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K0*,-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0*,0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0*,-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K0,0*
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K0,-0*
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0,0*
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:K-0,-0*
bo2bo$o$o3bo$4o!

Spheres also reject it outright:

Code: Select all

x = 5, y = 4, rule = B3/S23:S0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:S-0
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:S0*
bo2bo$o$o3bo$4o!

Code: Select all

x = 5, y = 4, rule = B3/S23:S-0*
bo2bo$o$o3bo$4o!

All 38 of these should work and behave as if no bounded grid was specified in the first place.

[confocaloid]

There's also some other cases of things being incorrectly considered patterns, such as this.

There will always be such cases since it's non-trivial to determine whether arbitrary text is an invalid pattern or not a pattern.

Is there a way to explicitly tell LifeViewer to ignore a given code box, and not display "Show in viewer" link for it? (regardless of whether or not the code box contains a pattern)

[rowett]

Is there a way to explicitly tell LifeViewer to ignore a given code box, and not display "Show in viewer" link for it? (regardless of whether or not the code box contains a pattern)

No.

[unname551]

Suggestion: LifeViewer supports reversible rules.

[rowett]

Suggestion: LifeViewer supports reversible rules.

What type of reversible rules are you after?

LifeViewer already supports reversible PCA and Margolus rules.

[unname551]

Reversible secondorder rule

[rowett]

Reversible secondorder rule

Please give some examples or links to a specification.

[unname551]

Reversible secondorder rule

Please give some examples or links to a specification.

https://en.wikipedia.org/wiki/Second-or ... _automaton

[muzik]

I don't think these cells should become state 2 when border killed?

Code: Select all

x = 15, y = 17, rule = B3/S23Super
5.W$3.2W$4.2W3$4.2W$3.4W.W$.W4.2W$W6.W.W3.W$3W5.2W2.W.W$8.2W3.W$4.W$3.
W7.W$3.3W4.2W$8.W$7.W$7.3W!
[[ STARTFROM 980 MAXGRIDSIZE 9 ]]

[muzik]

Identify classes the following as period 2000, mod 100, which does not correspond to a valid symmetry:

Code: Select all

x = 2, y = 3, rule = B3/S2-i34q:T20,20+19
o$2o$o!

For long period tables, it's possible to scroll far enough that the lowest period (in this case, 1) is at the top of the list. This is a bit inconsistent with the top, since you can't scroll up to a state where the highest period is at the bottom with empty space above it. Scrolling should probably be capped such that the lowest period cannot move any higher than the lowest entry on the list.

Code: Select all

x = 155, y = 144, rule = B3/S23
96b2o48b2o$97bo48bo$84b2o11bobo44bobo$83bo2bo11b2o9b2o22b3o8b2o$84b3o
20b2o2bo19bo3b2o$83bo3bo19bo2b3o2b2o10b2o2bobo2b2o$82bob4o19bo4bo2b2o
10b2obo5bo$69b2o11bobob2o20b5o18b5o$70bo12bobobobo$70bobo12b2obobo17b
5o18b5o$71b2o3bo8b4obo16bo4bo2b2o10b2obo5bo$77b2o6bo3bo17bo2b3o2b2o10b
2o2bobo2b2o$77b2o7b3o18b2o2bo19bo3b2o$66b2o5bo3bo3bo4bo2bo8b2o9b2o22b
3o8b2o$71bobo3bo3b3o3b2o8bobo44bobo$65bo3bo6b2o3b3o13bo48bo$64bo4bo6b
2o4b3o11b2o48b2o$63bobobo5b3o4b2o$62bobobo7b3o3b2o$56b2o2bo4bo8b3o3bo
3bobo31b2o6b2o$56b2o2bo3bo11bo3bo3bo32bo2bo4bo2bo$70bo2bo5b2o36bo2bo4b
o2bo$52bo9b2o6bo8b2o36bo2bo4bo2bo$51bobo15bo4bo6bo3b2o31b2o6b2o$52bo
15bobo2b2o10bobo$56b3obo5b2obo17bo$55bob2ob2o25b3o7b2o15b2o16b2o$55bo
5b2o27bo6bo17bo16bo$55b2o5bo3bo2bo19b2o4bobo17bob2o10b2obo$56b2ob2obo
5b2o25b2o19bo3bo6bo3bo$57bob3o29b3o12b2o13bo4bo$65bo25b3o11bo2bo8bo3bo
4bo3bo$64bobo38bobobo11bo4bo$65bo3bo18b2o16bo2bo6bo3bo6bo3bo$68bobo16b
obo4b2o14bo4bob2o10b2obo$60b2o6bobo16bo6bo12bobo5bo16bo$60b2o4b3o2b2o
13b2o7b3o16b2o16b2o$65b2o2bobo8bo16bo16bo38b2o$64bobob2o2bo6bobo15bob
2o10b2obo21bobo2b2o6b3o2bo$62b3obo3b2o3bo13b2o7bo3bo6bo3bo21bo2bo2bobo
8b2o$54b2o5bo4bob2o5bo2bo2bo4b2o2bo12bo4bo10b2o15b2obo3bo4bo$54bobo4b
2o3b2obo4bob2o7b2ob2o9bo3bo4bo3bo6b2o19b2ob2o3bo$56bo2b2o17b2o5b2o16bo
4bo31b2o2bo7b2o$47b2o6b2obobo14b2o2bo5b2o11bo3bo6bo3bo12b5o5b3o3b3o4b
3o2bo$47b2o9bo16b2o3b2o3b2ob2o7bob2o10b2obo11bo9bo2b2o12b2o$54b5o2bo
15bo8b2o2bo6bo16bo12bo2bo5b2ob2o$55bo3b3o17b3o7b2o5b2o16b2o12b2o7bo3bo
b2o$54b2ob2o66b2o10bobo2bo2bo$53bo5bo64bo2bo10b2o2bobo$53b6o47b2o20bo$
98bo6bobo3b2o11b5o$55b2o22b3o16b2o4bo2bo3b2o$55b2o12bo12bo4b3o12bo3bo
27b2o$69b2o7bo3bo3bo3bo11bobo29b2o$47b3o27bobo2bo2bo5bo$46bo3bo14bobo
2b3o2bo2bobo21bobo$45bo5bo13b4obo4bo3bo4bo7bo9bo3bo$46bo3bo14b2o8bo8bo
7bo5b2o4bo2bo3b2o$36b3o8b3o26b3o19bo6bobo3b2o8b2o15b2o$18b2o5b2o9b3o8b
3o35bo5bo14b2o13b2o15b2o$18b2o5b2o9b3o47bo3bo$18b2o5b2o6b3o51b3o$18bo
7bo6b3o39b2o$16b2ob2o3b2ob2o4b3o11b2o25bo2bo56b2o$16b2ob2o3b2ob2o18b2o
25bobobo55bobo$16b2o2bo3bo2b2o46bob3o49b3o$7b2o8b2obo3bob2o49b3o15bo2b
2o4b2o2bo19bo3bo$7bo2b3o5b2o5b2o67bo3b3o2b3o3bo17b2o3b2o$8b2o9bo5bo9b
2o58bo2b2o4b2o2bo19bo$13bo20b4o36b2o53b5o$13bo19bo2bobo33bo4bo52bo$8b
2o22bobo2b2o32bo6bo22b2o$7bo2b3o5b2o5b2o4bobo36bo8bo3b3o$7b2o9b2o5b2o
3b2o38bo8bo5bo17bo5bo20bo$18b2o5b2o3b3o37bo8bo4bo18bo5bo3bo13b5o$18bo
7bo4bobo37bo6bo22b4o3b4o20bo$16b2ob2o3b2ob2o3b2o38bo4bo22b2o9b2o14b2o
3b2o$16b2ob2o3b2ob2o45b2o23b3o2b2ob2o2b3o14bo3bo$5bobo8b2o2bo3bo2b2o
70b2o3b2ob2o3b2o15b3o$4bo2bo9b2obo3bob2o42bo2bo26b3obo3bob3o11bobo$4b
2o2b2o8b2o5b2o47bo26b2o7b2o13b2o$4bo4bo9bo5bo7b2o34bo5bo26b3o3b3o$b3o
5bo22bo2bo33b2o4bo28b2ob2o$obo5bo22bobobo38bo28bobobobo$7bo23bo2bo38bo
21b2o7bo3bo12b2o15b2o$2o4bobo9b2o5b2o3bo41b4obo17b2o24b2o15b2o$2bo2bob
obo2b2o4b2o5b2o4bobo38bo3bo$2b3o3bo3b2o56bo3bo21bo$34b2o33bob4o20bobo$
32bo4bo35bo16b2o2bo2bo4b3o3b3o$8b2o21bo6bo33bo17b2obo8b2obobob2o$8b2o
20bo8bo3b3o25bo4b2o16b2o9bobo$30bo8bo5bo25bo5bo$30bo8bo4bo27bo31b2ob2o
$31bo6bo34bo2bo6bo4bo$32bo4bo43b3o3bob2o$34b2o44bo6bobo5b2o$80b2o6bobo
3bobo$93b3o$74bob2o15b2o$73bo2bob2o14bobo$73bo2bo3bo14bobo2b2o$73b3o
20bo2bobo$68bo11bo16b4o$67bo11bo18b2o$72b3o$67bo3bo2bo$68b2obo2bo$70b
2obo$49bo$49b3o14b2o$52bo14bo$51b2o11b3o$64bo$62bobo$62b2o7$58bobo$57b
o2bo$57bo2bo$58bo2$53bo$51bo2bo$51bo2bo$51bobo7$48b2o$47bobo$47bo$46b
2o11b2o$59bo$60b3o$62bo!
[[ THEME Mono ]]

[Anivec]

Can the "clear history cells" button be replaced with a button that changes certain states in the selection to other states specified?
For example, I want to change all the state 3 cells in this pattern to state 5 cells:

Code: Select all

x = 54, y = 56, rule = LifeHistory
7$17.A$17.3A7.2A$20.A6.A$19.2A3.BA.A$19.4B.B2A$19.6B$18.7B$16.9B$14.
12B$13.12B$12.15B$11.4B.12B11.A$10.4B2.12B9.3A$9.4B2.13B8.A$9.3B3.14B
7.2A$9.2B4.14B3.6B4.2A$9.B5.21B6.A$14.4BC18B2.BA.A$14.4B2C18B.B2A$13.
6B2C13BA5B$12.7B3C11BABA5B$13.6B2C13BA5B$15.3B2C18B.B2A$15.3BC18B2.BA
.A$13.23B6.A$12.17B3.6B4.2A$11.20B5.2A$12.15B2.2A5.A$13.14B2.A7.3A$
13.14B3.3A6.A$13.13B6.A$13.13B$15.11B$15.11B$16.2DBD5B$17.3D2.B$18.D!

But you have to replace all the cells by hands, which is a massive problem for patterns with both states 2 and 4 or states 3 and 5.

[dvgrn]

Can the "clear history cells" button be replaced with a button that changes certain states in the selection to other states specified?
For example, I want to change all the state 3 cells in this pattern to state 5 cells...
But you have to replace all the cells by hands, which is a massive problem for patterns with both states 2 and 4 or states 3 and 5.

If you're working in a browser on a computer with a keyboard, first go into Edit mode and choose the state you want to change some cells to. Then select an area, hit Alt+K, and click on a sample cell with the state that you want to change. All cells of that state inside the selection will change.

Alt+K is the same shortcut used in Golly for the same functionality (ToChangeState.lua). I don't know offhand if there's a way to do the Alt+K trick on mobile.

[unname4798]

Can the "clear history cells" button be replaced with a button that changes certain states in the selection to other states specified?
For example, I want to change all the state 3 cells in this pattern to state 5 cells...
But you have to replace all the cells by hands, which is a massive problem for patterns with both states 2 and 4 or states 3 and 5.

If you're working in a browser on a computer with a keyboard, first go into Edit mode and choose the state you want to change some cells to. Then select an area, hit Alt+K, and click on a sample cell with the state that you want to change. All cells of that state inside the selection will change.

Alt+K is the same shortcut used in Golly for the same functionality (ToChangeState.lua). I don't know offhand if there's a way to do the Alt+K trick on mobile.

Connect keyboard to your tablet and press Alt+K (for Android) or Option+K (for iPad)

[Anivec]

Can the "clear history cells" button be replaced with a button that changes certain states in the selection to other states specified?
For example, I want to change all the state 3 cells in this pattern to state 5 cells...
But you have to replace all the cells by hands, which is a massive problem for patterns with both states 2 and 4 or states 3 and 5.

If you're working in a browser on a computer with a keyboard, first go into Edit mode and choose the state you want to change some cells to. Then select an area, hit Alt+K, and click on a sample cell with the state that you want to change. All cells of that state inside the selection will change.

Alt+K is the same shortcut used in Golly for the same functionality (ToChangeState.lua). I don't know offhand if there's a way to do the Alt+K trick on mobile.

It's not working, unless I should be be pressing another key. I don't have and "Alt" key on a IOS keyboard, is there something I should be pressing instead?

[dvgrn]

It's not working, unless I should be be pressing another key. I don't have and "Alt" key on a IOS keyboard, is there something I should be pressing instead?

I don't have an iOS keyboard handy at the moment, so please don't take me as any kind of expert on this. But Google says

The Option key is the Apple equivalent of Alt. "Option" and "Alt" are used interchangeably. For anything you see that requires the Alt key, use Option.

[rowett]

Here is implementation of [R]Investigator:

LifeViewer now has experimental support for [R]Extended (which is a native implementation of the StateInvestigator rule family).

[PHPBB12345]

LifeViewer now has experimental support for [R]Extended (which is a native implementation of the StateInvestigator rule family).

Example:

Code: Select all

x = 50, y = 1, rule = MAPAAD//zAwPz8AAP//MDA/PwAA//8AAP//AAD//wAA//8AAD8/AAD//wAAPz8AAP//wMD//wAA///AwP//AAD//wInvestigator 
50A!

Compare:

Code: Select all

x = 50, y = 1, rule = MAPAAD//zAwPz8AAP//MDA/PwAA//8AAP//AAD//wAA//8AAD8/AAD//wAAPz8AAP//wMD//wAA///AwP//AAD//w
50o!

[rowett]

Code: Select all

x = 50, y = 1, rule = MAPAAD//zAwPz8AAP//MDA/PwAA//8AAP//AAD//wAA//8AAD8/AAD//wAAPz8AAP//wMD//wAA///AwP//AAD//wExtended
50A!

Fixed, thanks!

[PHPBB12345]

What about [R]Extended with B0?

[unname4798]

What about [R]Extended with B0?

For [R]Extended B0/D8 rules, do the following: Invert birth and survival conditions.

[unname4798]

Should patterns that die out not pause playback themselves if there is a STOP command scheduled for execution after the pattern dies?