Pattern viewer for forum threads

[rowett]

You doubleposted.

Yes, I know. Sometimes I will if I'm answering multiple different topics.

[b-engine]

I cannot immediately paste clipboard into LifeViewer until I copy something first (even when sync off). Could the paste button enabled by default?

[rowett]

I cannot immediately paste clipboard into LifeViewer until I copy something first (even when sync off). Could the paste button enabled by default?

Yes, it's now enabled when External Sync is active.

[muzik]

Another way I've been thinking of for handling hexagonal selections would be as follows:

Code: Select all

x = 1, y = 1, rule = B123456/S0123456HHistory
E!
[[ GRID AUTOSTART PAUSE 1 GPS 1 COLOR mark2 0 0 255 ARROWTRACK 0 -1 ARROW 1.5 1.5 0.5 0.5 32 ]]

Instead of having to define two vertices and drawing a hexagon between both of them, we would instead use the initial click as the center, and then draw a perfect hexagon shape around it whose size is the distance of the cursor from the center. Perhaps more restrictive since the hexagon must be regular, but it's simple, should work, and any flipping/rotation of selections would keep the selection shape identical to what it previously was.

Also, while preparing that above example, something weird I noticed:

Code: Select all

x = 1, y = 1, rule = B/S0123456H
o!
[[ GRID AUTOSTART PAUSE 1 AUTOFIT ]]

The other two grid types are not affected:

Code: Select all

x = 1, y = 1, rule = B/S012345678
o!
[[ GRID AUTOSTART PAUSE 1 AUTOFIT ]]

Code: Select all

x = 1, y = 1, rule = B/S0123456789XYZL
o!
[[ GRID AUTOSTART PAUSE 1 AUTOFIT ]]

[rowett]

Another way I've been thinking of for handling hexagonal selections would be as follows:

Very nice animation!

I'll give this more thought when I have time.

Also, while preparing that above example, something weird I noticed:

Fixed, thanks!

[pifricted]

Emulating W37(Sorry^3, It is not wrong):

Code: Select all

x = 1, y = 1, rule = W218|W164
o!

The side of pattern will grow, but it work:

Code: Select all

x = 43, y = 14, rule = B/S012345678History
F13.F$F13.F$F13.F$F6.A6.F9.A$F4A2.A2.4AF8.A.A$F5.3A5.F8.3A$F4A5.4AF7.
5A$F5.3A5.F8.3A$F4A5.4AF7.5A$F5.3A5.F8.3A$F4A5.4AF7.5A$F13.F$F13.F$F13.
F!

May LifeViewer support 1D CA with odd Woifram code?

[rowett]

Emulating W37(Sorry^3, It is not wrong):

Code: Select all

x = 1, y = 1, rule = W218|W164
o!

May LifeViewer support 1D CA with odd Woifram code?

Added, thanks.

Code: Select all

x = 1, y = 1, rule = W37
o!

[b-engine]

Emulating W37(Sorry^3, It is not wrong):

Code: Select all

x = 1, y = 1, rule = W218|W164
o!

May LifeViewer support 1D CA with odd Woifram code?

Added, thanks.

Code: Select all

x = 1, y = 1, rule = W37
o!

It seems behave incorrectly:

Code: Select all

#C What W101 behaves on LifeViewer
x = 1, y = 1, rule = W101
o!

What should W101 actually behaves, from Wolfram|Alpha

W101.png (8.06 KiB) Viewed 2519 times

Maybe use another way to emulate it?

[pifricted]

It seems behave incorrectly:

Code: Select all

#C What W101 behaves on LifeViewer
x = 1, y = 1, rule = W101
o!

W101.png
Maybe use another way to emulate it?

Rule:W101

Maybe an idea.

[unname4798]

It seems behave incorrectly:

Code: Select all

#C What W101 behaves on LifeViewer
x = 1, y = 1, rule = W101
o!

W101.png
Maybe use another way to emulate it?

Rule:W101

Maybe an idea.

Another Idea: (W1 as an example)

Code: Select all

#R R1,C2,S3,B,NW000201000|R1,C2,S0-3,B1-3,NW000201000
o!
[[ RANDOMIZE ]]

[muzik]

What exactly does Scale represent in Help > Info > Display, and is there any way to change it? On desktop it appears to be locked at 1.00 regardless of window size, but on the iPad I've mentioned it varies depending on whether tabs are visible or not. If I had an easy method of changing this on desktop I could set up a simple test case for the hexagonal period map bug I mentioned earlier.

[b-engine]

I don't like when I have accidentally tap a wrong key when changing rulestring, then clicking OK results in an error and the rulestring (especially Hensel notation) unretrievable. Could the rulestring kept even when LifeViewer errors out?

[rowett]

What exactly does Scale represent in Help > Info > Display, and is there any way to change it?

There are three related items:

• Pixel Ratio is the ratio of the resolution in physical pixels to the resolution in CSS pixels on the current device. See here for more information. It is typically 1 for normal screens and 2 for high DPI screens. However, if you scale the browser window this will change.
• Scale is the scaling factor that LifeViewer applies to the PopUp Viewer window. It will be the same as Pixel Ratio unless that makes the Popup Viewer too big to fit in the browser window, it which case it will be reduced to compensate, but never less than 1.
• Window Zoom is typically 1, but will be less than 1 if the Pixel Ratio is so high that a Scale of 1 is not enough to fit the Popup Viewer in the browser, in which case it will be less than 1.

The reason both Scale and Window Zoom exist is for display fidelity. If the window needs to grow from 1x size it looks nicer just to use Scale to create bigger fonts, draw larger controls and so on - rather than drawing everything at 1x and asking the browser to scale the window.

If the window needs to shrink below 1x then it looks nicer to render everything at 1x and then ask the browser to scale it to make it smaller.

[rowett]

I don't like when I have accidentally tap a wrong key when changing rulestring, then clicking OK results in an error and the rulestring (especially Hensel notation) unretrievable. Could the rulestring kept even when LifeViewer errors out?

Added in build 1175.

[unname4798]

I don't like when I have accidentally tap a wrong key when changing rulestring, then clicking OK results in an error and the rulestring (especially Hensel notation) unretrievable. Could the rulestring kept even when LifeViewer errors out?

And the pattern?

[rowett]

I don't like when I have accidentally tap a wrong key when changing rulestring, then clicking OK results in an error and the rulestring (especially Hensel notation) unretrievable. Could the rulestring kept even when LifeViewer errors out?

And the pattern?

Settings>Pattern>Open Pattern (hotkey Ctrl-O)

[rowett]

It seems behave incorrectly:

Code: Select all

#C What W101 behaves on LifeViewer
x = 1, y = 1, rule = W101
o!

It behaves better now.

[muzik]

Could we get 3-state emulation for alternating 1D rules as well?

Code: Select all

x = 18, y = 1, rule = W60|W102
2ob5o2b2obobobo!

[b-engine]

It behaves better now.

The alternating red and yellow causes sore on my eyes. Can the cell colors be the same (and possibly match the theme color)?

[unname4798]

XRecorder_Edited_28072024_083126.jpg (443.48 KiB) Viewed 2391 times

What is that? -1 alive cells. How is that possible?

[pifricted]

Code: Select all

x = 21, y = 7, rule = W101Super
4A3.3A2.4A.4B$A3.A3.A3.A4.B2.B$A3.A3.A3.A7.B$A3.A3.A3.4A3.2B$A3.A3.A3.
A6.B$A3.A3.A3.A$4A3.3A2.4A3.B!

Why did history cell is "alive"?
Why did state-1 cell we draw will die?
(Looks unfinished.)

edit:the deleted state-1 cell will come back next gen.

[unname4798]

Code: Select all

x = 21, y = 7, rule = W101Super
4A3.3A2.4A.4B$A3.A3.A3.A4.B2.B$A3.A3.A3.A7.B$A3.A3.A3.4A3.2B$A3.A3.A3.
A6.B$A3.A3.A3.A$4A3.3A2.4A3.B!

Why did history cell is "alive"?
Why did state-1 cell we draw will die?
(Looks unfinished.)

edit:the deleted state-1 cell will come back next gen.

And also, W101History copies colors from states 3-6 from the last rule. (in Draw tab)
In reality, these states are actually state 2.

[pifricted]

And also, W101History copies colors from states 3-6 from the last rule. (in Draw tab)
In reality, these states are actually state 2.
In W101Investigator, state 1 is Life.

On my computer, state 1 in W101Investigator will death.

In W101Super, birth and alive total are strange.
In W101 history,we can't draw state 3-6.It'll draw state-2.

[muzik]

I assume that specifying "circles", "hexagons", etc. in @ICONS is also going to remain unsupported?

Period maps for triangular rules seem quite blurry to me:

Code: Select all

x = 6, y = 4, rule = B4/S456L
3bo$b5o$b5o$3bo!
[[ AUTOIDENTIFY ]]

Code: Select all

x = 7, y = 5, rule = B45/S23L
$2b2obo$bo4bo$2o4bo$bo3bo!
[[ AUTOIDENTIFY ]]

Code: Select all

x = 5, y = 4, rule = B4/S345L
3bo$o$b4o$3bo!
[[ AUTOIDENTIFY ]]

Code: Select all

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

Same for hexagonal rules:

Code: Select all

x = 3, y = 3, rule = B2/SH
bo$o$2bo!
[[ AUTOIDENTIFY ]]

Code: Select all

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

Code: Select all

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

But not square grids:

Code: Select all

x = 3, y = 1, rule = B3i/S2i
3o!
[[ AUTOIDENTIFY ]]

Code: Select all

x = 3, y = 1, rule = B2c/S
obo!
[[ AUTOIDENTIFY ]]

Code: Select all

x = 3, y = 1, rule = B2i3i/S0
3o!
[[ AUTOIDENTIFY ]]

Code: Select all

x = 3, y = 1, rule = B2ci/S1e
obo!
[[ AUTOIDENTIFY ]]

[rowett]

The alternating red and yellow causes sore on my eyes. Can the cell colors be the same (and possibly match the theme color)?

I've changed the colours to be based on the default Theme. The two state colours are slightly different since they are two different states and it's helpful for editing.

Could we get 3-state emulation for alternating 1D rules as well?

Code: Select all

x = 18, y = 1, rule = W60|W102
2ob5o2b2obobobo!

No. Effort vs impact.

What is that? -1 alive cells. How is that possible?

Why did history cell is "alive"?
Why did state-1 cell we draw will die?
(Looks unfinished.)
edit:the deleted state-1 cell will come back next gen.

And also, W101History copies colors from states 3-6 from the last rule. (in Draw tab)
In reality, these states are actually state 2.

On my computer, state 1 in W101Investigator will death.

In W101Super, birth and alive total are strange.
In W101 history,we can't draw state 3-6.It'll draw state-2.

The Wolfram RuleTable emulation does not support [R]Super, [R]History or [R]Investigator. These rules will now be reported as errors.