Pattern viewer for forum threads

[bubblegum]

And the slider which controls the fill amount of the random fill, 100% is not at the end of the bar and it's possible, if you slide it slowly, to set it to 101%

Please will you post a screenshot of both the slider at 100% but not at the end of the bar, and also the 101%.

Now that I think of it, the 100% thing doesn't really count, but the 101% does:


The 101% is rightfully fused to the end of the slider area.

[rowett]

The 101% is rightfully fused to the end of the slider area.

Thanks. I've posted a potential fix but still can't reproduce so please let me know if you still see it with build 567.

[bubblegum]

The 101% is rightfully fused to the end of the slider area.

Thanks. I've posted a potential fix but still can't reproduce so please let me know if you still see it with build 567.

Fixed, thanks.

[GUYTU6J]

Why is SHOW IN VIEWER displayed on a code box containing no pattern codes?

...

Code: Select all

! /bin/sh
# Add LifeViewer to the Life Lexicon

# define input and output file names
input=lex.html
output1=lex1.html
output2=lex2.html
output3=lexlv.html

# insert the LifeViewer plugin into the head section
cat $input | sed 's@</head>@<meta name="LifeViewer" content="viewer pre 150">\n<script src="lv-plugin.js"></script>\n&@' > $output1

# add a show in viewer button to each pattern
cat $output1 | sed 's@<pre>@<div class="viewer">\n<button type="button" onclick="updateViewer(this);return false;">Show in Viewer</button>\n&@' > $output2
cat $output2 | sed 's@</pre>@&\n</div>\n@' > $output3

# tidy up
rm -f $output1 $output2

[rowett]

Why is SHOW IN VIEWER displayed on a code box containing no pattern codes?

Because ! marks the end of an RLE pattern so it's valid. Everything after the ! is considered as comments.

[PHPBB12345]

Suggestion: Margolus Generation (multi-state)
e.g. M0,8,4,3,2,5,9,7,1,6,10,11,12,13,14,15,3 is 3-state rule

[rowett]

Suggestion: Margolus Generation (multi-state)
e.g. M0,8,4,3,2,5,9,7,1,6,10,11,12,13,14,15,3 is 3-state rule

Thanks for the suggestion. This isn't a priority at the moment and would be quite tricky to implement (especially for reversible rules) so I don't know if and when I'll get to it.

[bubblegum]

Multistate rules now draw with 1 if the selected state is not 0, and smart drawing is effectively off.

Please post a pattern that reproduces that behaviour.

Code: Select all

#C [[ PASTET 1 PASTE E! 0 1 ]]
x = 3, y = 1, rule = LifeHistory
3A!

Code: Select all

#C [[ PASTET 1 PASTE B! 0 1 ]]
x = 3, y = 1, rule = DeadlyEnemies
3A!

Note that the PASTE command is given states 5 and 2 yet produces state 1 for both.

Also I need one of two things:
1) A way to specify weights 8-f/80-ff being 8~15/128~255 instead of being negative, or
2) Negative birth and survival conditions.

[lemon41625]

This should work look like this I think:

Code: Select all

x = 16, y = 18, rule = R2,C2,S3-4,B3-4,NW0000001110010100111000000|R2,C2,S3-4,9-20,B4,NW1111111111110111111111111
9b3o5b$9bo7b$9b4o4b$17b$17b$17b$17b$17b$b3o13b$4o13b$2o15b$2o15b$17b$13b2o2b$12bo2bob$11bo4bo$11bo4bo$12bo2bob$13b2o2b$!

If alternating between neighbourhoods isn't supposed to work, an error message should probably be shown.

Alternating rules error handling also seems a bit wonky when a user tries to input 2 different rule families.

[bubblegum]

Code: Select all

03ajkr/2ak/3 - Fireworld

I am getting sick of the contrasting ruletable/Generations colours.

[muzik]

Will LifeSuper be able to support history fading effects like LifeHistory and other rules (shortened, of course, as to fit within the 256 state limit)?

[muzik]

Can aliases that duplicate the weighted aliases be removed in favour of the weighted aliases if the rules in question behave identically (or, equivalently, all range-1 weighted aliases be converted to the other rulespace formats in question)?

SolarWorld also seems to be slightly misplaced.

[ColorfulGalaxy]

I failed to color the states 14 and 16 in LifeSuper.
Reproduce this bug

Code: Select all

x = 26, y = 74, rule = LifeSuper
24.2P$23.P.P$22.P$21.P$20.P$19.P$18.P$17.P$16.P$15.P$12.P.P$12.2P4$11.
2P$10.P2.P$11.2P3$8.P$7.P.P$7.2P3$11.P$10.P.P$9.P.P$10.P3$8.P$7.P.P$8.
P4$9.2P$9.2P4$4.M6.M$3.M.M.2M.M.M$3.2M2.2M2.2M$7.2M2$5.2M2.2M$5.2M2.2M
$6.4M$6.M2.M$5.M4.M$5.M4.M$5.M.2M.M$6.M2.M$6.M2.M2$M14.M$2M4.M2.M4.2M
$M5.4M5.M$.2M4.2M4.2M$2.M10.M$M.M10.M.M$.5M4.5M$3.M2.4M2.M$2.M4.2M4.M
$6.M2.M$7.2M$4.2M.2M.2M2$3.M8.M$2.3M6.3M$2.M2.M4.M2.M$.2M10.2M!
[[ COLOR 14 255 255 255 ]] [[ COLOR 16 255 255 255 ]]

Code: Select all

x = 26, y = 74, rule = LifeSuper
24.2P$23.P.P$22.P$21.P$20.P$19.P$18.P$17.P$16.P$15.P$12.P.P$12.2P4$11.
2P$10.P2.P$11.2P3$8.P$7.P.P$7.2P3$11.P$10.P.P$9.P.P$10.P3$8.P$7.P.P$8.
P4$9.2P$9.2P4$4.M6.M$3.M.M.2M.M.M$3.2M2.2M2.2M$7.2M2$5.2M2.2M$5.2M2.2M
$6.4M$6.M2.M$5.M4.M$5.M4.M$5.M.2M.M$6.M2.M$6.M2.M2$M14.M$2M4.M2.M4.2M
$M5.4M5.M$.2M4.2M4.2M$2.M10.M$M.M10.M.M$.5M4.5M$3.M2.4M2.M$2.M4.2M4.M
$6.M2.M$7.2M$4.2M.2M.2M2$3.M8.M$2.3M6.3M$2.M2.M4.M2.M$.2M10.2M!
[[ COLOR 13 255 15 255 ]]

[dvgrn]

I failed to color the states 14 and 16 in LifeSuper.
Reproduce this bug

I don't think there's any bug here, but maybe you can explain it better. States 14 and 16 are even-numbered states, so they're OFF cells, meant for use as annotations, not as actual pattern cells. No matter what you draw in state 16, it will just sit there, and the bulldozer spaceship will happily bulldoze over it -- and so would any other sufficiently wide spaceship:

Code: Select all

x = 16, y = 48, rule = LifeSuper
4.P6.P$3.P.P.2P.P.P$3.2P2.2P2.2P$7.2P2$5.2P2.2P$5.2P2.2P$6.4P$6.P2.P$
5.P4.P$5.P4.P$5.P.2P.P$6.P2.P$6.P2.P2$P14.P$2P4.P2.P4.2P$P5.4P5.P$.2P
4.2P4.2P$2.P10.P$P.P10.P.P$.5P4.5P$3.P2.4P2.P$2.P4.2P4.P$6.P2.P$7.2P$
4.2P.2P.2P2$3.P8.P$2.3P6.3P$2.P2.P4.P2.P$.2P10.2P10$7.3M$6.M2.M$9.M$
5.M3.M$5.M3.M$9.M$6.M.M!

State 14 is a label state that disappears after one tick, so that won't persist for long. State 16 is a label state that persists until it is touched by a live cell, and then it switches to state 14 and disappears in a reaction that spreads to all nearby state-16 cells at lightspeed -- as you can see in the final object touched by the spaceship in your pattern: no block is left behind at the end, unlike what would happen if those were real ON cells.

[ColorfulGalaxy]

I failed to color the states 14 and 16 in LifeSuper.
Reproduce this bug

I don't think there's any bug here, but maybe you can explain it better. States 14 and 16 are even-numbered states, so they're OFF cells, meant for use as annotations, not as actual pattern cells. No matter what you draw in state 16, it will just sit there, and the bulldozer spaceship will happily bulldoze over it -- and so would any other sufficiently wide spaceship:

Code: Select all

x = 16, y = 48, rule = LifeSuper
4.P6.P$3.P.P.2P.P.P$3.2P2.2P2.2P$7.2P2$5.2P2.2P$5.2P2.2P$6.4P$6.P2.P$
5.P4.P$5.P4.P$5.P.2P.P$6.P2.P$6.P2.P2$P14.P$2P4.P2.P4.2P$P5.4P5.P$.2P
4.2P4.2P$2.P10.P$P.P10.P.P$.5P4.5P$3.P2.4P2.P$2.P4.2P4.P$6.P2.P$7.2P$
4.2P.2P.2P2$3.P8.P$2.3P6.3P$2.P2.P4.P2.P$.2P10.2P10$7.3M$6.M2.M$9.M$
5.M3.M$5.M3.M$9.M$6.M.M!

State 14 is a label state that disappears after one tick, so that won't persist for long. State 16 is a label state that persists until it is touched by a live cell, and then it switches to state 14 and disappears in a reaction that spreads to all nearby state-16 cells at lightspeed -- as you can see in the final object touched by the spaceship in your pattern: no block is left behind at the end, unlike what would happen if those were real ON cells.

The real matter is, I couldn't color these cells using scripts.

[dvgrn]

The real matter is, I couldn't color these cells using scripts.

Ah, I see now, you're looking to hide the fact that those are actually OFF states, maybe for trolling purposes.

I don't see how to get these to work, either:

Code: Select all

[[ COLOR 14 255 255 255 ]]
[[ COLOR 16 255 255 255 ]]

An associated minor issue: the Help for this says COLOR <0..16> R G B. The "16" doesn't seem like the right maximum value nowadays.

EDIT: I don't seem to be able to change any LifeSuper colors, but it works fine for other rules. Here's state-2 coloring in LifeSuper, LifeHistory, and 'none' rules:

Code: Select all

x = 19, y = 48, rule = LifeSuper
6.B6.B$5.B.B.2B.B.B$5.2B2.2B2.2B$9.2B2$7.2B2.2B$7.2B2.2B$8.4B$8.B2.B$
7.B4.B$7.B4.B$7.B.2B.B$8.B2.B$8.B2.B2$2.B14.B$2.2B4.B2.B4.2B$2.B5.4B
5.B$3.2B4.2B4.2B$4.B10.B$2.B.B10.B.B$3.5B4.5B$5.B2.4B2.B$4.B4.2B4.B$
8.B2.B$9.2B$6.2B.2B.2B2$5.B8.B$4.3B6.3B$4.B2.B4.B2.B$3.2B10.2B10$2.3M
4.3M4.3M$.M2.M3.M2.M3.M2.M$4.M6.M6.M$M3.M2.M3.M2.M3.M$M3.M2.M3.M2.M3.
M$4.M6.M6.M$.M.M4.M.M4.M.M!
[[ COLOR 2 White ]]

Code: Select all

x = 19, y = 48, rule = LifeHistory
6.B6.B$5.B.B.2B.B.B$5.2B2.2B2.2B$9.2B2$7.2B2.2B$7.2B2.2B$8.4B$8.B2.B$
7.B4.B$7.B4.B$7.B.2B.B$8.B2.B$8.B2.B2$2.B14.B$2.2B4.B2.B4.2B$2.B5.4B
5.B$3.2B4.2B4.2B$4.B10.B$2.B.B10.B.B$3.5B4.5B$5.B2.4B2.B$4.B4.2B4.B$
8.B2.B$9.2B$6.2B.2B.2B2$5.B8.B$4.3B6.3B$4.B2.B4.B2.B$3.2B10.2B10$2.3A
4.3A4.3A$.A2.A3.A2.A3.A2.A$4.A6.A6.A$A3.A2.A3.A2.A3.A$A3.A2.A3.A2.A3.
A$4.A6.A6.A$.A.A4.A.A4.A.A!
[[ COLOR 2 White ]]

Code: Select all

x = 19, y = 48, rule = none
6.B6.B$5.B.B.2B.B.B$5.2B2.2B2.2B$9.2B2$7.2B2.2B$7.2B2.2B$8.4B$8.B2.B$
7.B4.B$7.B4.B$7.B.2B.B$8.B2.B$8.B2.B2$2.B14.B$2.2B4.B2.B4.2B$2.B5.4B
5.B$3.2B4.2B4.2B$4.B10.B$2.B.B10.B.B$3.5B4.5B$5.B2.4B2.B$4.B4.2B4.B$
8.B2.B$9.2B$6.2B.2B.2B2$5.B8.B$4.3B6.3B$4.B2.B4.B2.B$3.2B10.2B10$2.3M
4.3M4.3M$.M2.M3.M2.M3.M2.M$4.M6.M6.M$M3.M2.M3.M2.M3.M$M3.M2.M3.M2.M3.
M$4.M6.M6.M$.M.M4.M.M4.M.M!
[[ COLOR 2 White ]]

[ColorfulGalaxy]

maybe for trolling purposes.

Yes, I tried to make a troll, but failed because of coloring issues.

Coloring works in many other rules like Immigration and Symbiosis.

[Hunting]

maybe for trolling purposes.

Yes, I tried to make a troll, but failed because of coloring issues.

Coloring works in many other rules like Immigration and Symbiosis.

LifeSuper is directly implemented in the viewer, while Immigration and the like are simulated using rule tables.

[bubblegum]

LifeSuper is directly implemented in the viewer, while Immigration and the like are simulated using rule tables.

LifeHistory and LifeSuper, likely for this reason, are uncolourable (this wasn't the case before).

[rowett]

An associated minor issue: the Help for this says COLOR <0..16> R G B. The "16" doesn't seem like the right maximum value nowadays.

Fixed, thanks.

I don't seem to be able to change any LifeSuper colors, but it works fine for other rules.

Fixed, thanks.

[bubblegum]

I don't seem to be able to change any LifeSuper colors, but it works fine for other rules.

Fixed, thanks.

The LifeHistory colouring example only works if you manually switch the rule to LifeSuper.

[rowett]

I don't seem to be able to change any LifeSuper colors, but it works fine for other rules.

Fixed, thanks.

The LifeHistory colouring example only works if you manually switch the rule to LifeSuper.

At the moment [R]History rules need state names for the colouring to work. I'll allow state numbers in a future release:

Code: Select all

# Type or paste RLE data into this box and click on the View button.
x = 9, y = 5, rule = B3/S23History
.ABCDEF!
[[
   COLOR OFF Blue
   COLOR ON Pink
   COLOR HISTORY Green
   COLOR MARK1 Purple
   COLOR MARKOFF Gold
   COLOR MARK2 Yellow
   COLOR KILL Red
]]

[ColorfulGalaxy]

An associated minor issue: the Help for this says COLOR <0..16> R G B. The "16" doesn't seem like the right maximum value nowadays.

Fixed, thanks.

I don't seem to be able to change any LifeSuper colors, but it works fine for other rules.

Fixed, thanks.

Now my bulldozer troll works.

[bubblegum]

Which build of LifeViewer automatically aliased rules when copying to clipboard for the express purpose of reliably erroring when pasting into Golly and can that not happen?

[dvgrn]

Which build of LifeViewer automatically aliased rules when copying to clipboard for the express purpose of reliably erroring when pasting into Golly and can that not happen?

Ow, this is a grumpy and slightly cryptic bug report. It was very tempting to answer it with

"No build of LifeViewer was done for the express purpose of reliably erroring -- that just happens naturally!"

and then wait for another post with an actual example of the problem.

I think I understand the issue, though. Let's say I have something like a HighLife bomber:

Code: Select all

x = 9, y = 14, rule = B36/S23
bo$bo$bo3$3bo$2b2o$bobo$3o2$6b3o$5bobo$5b2o$5bo!

Copying this out of LifeViewer, instead of using the Select All button and copying the original text, results in RLE with an aliased rule string:

Code: Select all

x = 9, y = 14, rule = HighLife
bo$bo$bo3$3bo$2b2o$bobo$3o2$6b3o$5bobo$5b2o$5bo!

I actually don't understand why that particular RLE can't be parsed by Golly, because "HighLife" is in fact a named rule that can be chosen from the Set Rule dialog. Apparently I've forgotten how named rules work in Golly. But in general I can see how this isn't the best behavior, because in the general case it's less likely to produce RLE that Golly can handle.