ConwayLife.com

Posted: **February 1st, 2022, 10:58 am**

Build 698 is now available on the lazyslug server

Fixes in this build:

fix [R]History rendering glitch after ZOOM < 16x
only show grid borders when both height and width at maximum

Posted: **February 2nd, 2022, 11:35 am**

Are rules in LV currently being pulled from URLs like https://conwaylife.com/wiki/Rule:Methlife

If so, could I request that the URL that LV requests is changed to something like https://conwaylife.com/wiki/Rule:Methlife?action=raw

The "?action=raw" (which you may already be using -- apologies if I missed it) would save me a bit of server resources, because then things like MediaWiki CSS templates etc, which aren't needed by LV, won't be called too.

Posted: **February 2nd, 2022, 12:11 pm**

Build 699 is now available on the lazyslug server

Enhancements in this build:

the optional rule name postfix specified with the <meta> tag now allows postfixes beginning with "?"
- <meta name="LifeViewer" content="/wiki/Rule: ?action=raw">

Posted: **February 2nd, 2022, 12:13 pm**

Nathaniel wrote: February 2nd, 2022, 11:35 am Are rules in LV currently being pulled from URLs like https://conwaylife.com/wiki/Rule:Methlife

Yes

Nathaniel wrote: February 2nd, 2022, 11:35 am If so, could I request that the URL that LV requests is changed to something like https://conwaylife.com/wiki/Rule:Methlife?action=raw

Yes. On the forum you'll need to modify the <meta name="LifeViewer"> tag to the following:

Code: Select all

<meta name="LifeViewer" content="rle code 37 hide limit /wiki/Rule: ?action=raw">

Posted: **February 2nd, 2022, 1:38 pm**

rowett wrote: February 2nd, 2022, 12:13 pm Yes. On the forum you'll need to modify the <meta name="LifeViewer"> tag to the following:
Code: Select all
<meta name="LifeViewer" content="rle code 37 hide limit /wiki/Rule: ?action=raw">

Thanks. I did that and cleared all caches, so I can see the meta tag on the forums, and I refreshed LV, so my computer has the latest build that has been uploaded to conwaylife.com. However, when I look at Chrome's network traffic viewer, it shows that LV is still pinging the wiki pages without "?action=raw". Can you check if it's working on your end?

Posted: **February 2nd, 2022, 4:01 pm**

Build 700 is now available on the lazyslug server

Fixes in this build:

allow extra parameters in <meta> settings

Posted: **February 2nd, 2022, 4:02 pm**

Nathaniel wrote: February 2nd, 2022, 1:38 pm However, when I look at Chrome's network traffic viewer, it shows that LV is still pinging the wiki pages without "?action=raw". Can you check if it's working on your end?

Fixed, thanks.

Posted: **February 22nd, 2022, 2:50 am**

Build 701 is now available on the lazyslug server

Fixes in this build:

fixed an issue with stop generation and Themes with no history

Posted: **February 23rd, 2022, 5:22 am**

Build 702 is now available on the lazyslug server

Fixes in this build:

fixed an issue with copying Themes

Posted: **February 25th, 2022, 5:09 am**

Build 703 is now available on the lazyslug server

Enhancements in this build:

maximum grid boundary is now always drawn

Posted: **February 25th, 2022, 8:11 am**

Build 704 is now available on the lazyslug server

Enhancements in this build:

don't use alias names for rule when saving RLE

Posted: **February 28th, 2022, 6:23 am**

Build 705 is now available on the lazyslug server

Enhancements in this build:

grey out rather than hide Settings Menu button when window too short
disable Major Gridlines button when [[ GRIDMAJOR 0 ]] set

Posted: **February 28th, 2022, 8:13 am**

Build 706 is now available on the lazyslug server

Fixes in this build:

disable Identify, Fast Identify, Go to Gen and [[ STARTFROM ]] for [[ VIEWONLY ]] patterns
don't assume Generations rule for multi-state patterns if pattern failed to decode

Posted: **March 4th, 2022, 1:27 pm**

Build 707 is now available on the lazyslug server

Enhancements in this build:

performance improvement when rendering 2-state patterns using Themes with no history

Posted: **March 10th, 2022, 10:57 am**

Build 708 is now available on the lazyslug server

Enhancements in this build:

Settings->Pattern->Go To Gen now supports trailing B for benchmark mode in the generation specification (e.g. 250B)

Posted: **March 10th, 2022, 10:58 am**

Build 709 is now available on the lazyslug server

Enhancements in this build:

Settings->Pattern->Save Image and Save Graph will now download the image in the browser

Posted: **April 24th, 2022, 4:24 pm**

Just ran into an oddity of the message-display system, maybe related to big step sizes or larger T values?

Code: Select all

x = 15926, y = 16272, rule = B3/S23
2bo$obo$b2o542$132bo$133bo$131b3o290$135b2o$134bobo$136bo$431b2o$430b
2o$432bo17$105bo$105b2o$104bobo7497$15923bobo$15923b2o$15924bo17$8105b
o$8106b2o$8105b2o$15893bo$15893bobo$15893b2o7448$99bobo$100b2o$100bo
17$427bo$425b2o$426b2o$131bo$129bobo$130b2o90$481bobo$481b2o$482bo198$
126b3o$128bo$127bo18$15896b3o$15896bo$15897bo74$478b3o$478bo$479bo$
187b2o$186bobo$188bo25$501b2o$500b2o$502bo!
#C [[ MAXGRIDSIZE 14 STEP 64 ]]
#C [[ T 1 ]]
#C [[ STOP 32000 "Glider streams heading for epicentre" ]]
#C [[ T 40430 PAUSE 5 "Bit-Reading Glider #1 heading for SE GPSE" ]]
#C [[ T 48380 PAUSE 5 "'1' signal heading NE to epicentre" ]]
#C [[ T 52390 PAUSE 5 "Bit-Reading Glider #2 heading for SE GPSE" ]]
#C [[ T 56170 PAUSE 5 "'2' signal heading NE to epicentre" ]]
#C [[ T 58120 PAUSE 5 "Bit-Reading Glider #3 heading for SE GPSE" ]]
#C [[ T 60660 PAUSE 5 "'1' signal heading NE to epicentre" ]]
#C [[ T 61610 PAUSE 5 "Bit-Reading Glider #4 heading for SE GPSE" ]]
#C [[ T 62200 PAUSE 5 "'1' signal heading NE to epicentre" ]]

I think the second and following messages definitely shouldn't be displayed until after T=32000. Not sure what's going on here exactly. See also this version -- the problem doesn't have to do with the STOP command, it seems. In that version, I think the first message should be displayed right away (at T=1 and on), but it currently takes a while to show up.

Originally I wanted to put in multiple STOP values. I remember there's a reason why multiple STOP commands aren't possible (any more?) but I guess I need a reminder about what the reason was.

More or less the same thing happens in this version, with no STOP command.

Posted: **April 25th, 2022, 11:19 am**

dvgrn wrote: April 24th, 2022, 4:24 pm Just ran into an oddity of the message-display system, maybe related to big step sizes or larger T values?

Firstly the [[ STOP 32000 ]] needs to appear before the first waypoint definition [[ T 1 ]]. At the moment only one [[ STOP ]] is supported. I had planned to allow multiple STOPs but never got round to completing it. At the moment if the [[ STOP ]] is defined at a Waypoint it is silently ignored.

Secondly [[ STOP ]] itself is not considered a waypoint so have a message at it is not relevant. The message is related to the current Waypoint definition and means: show this message until you reach the Waypoint target. This means that [[ T 1 STOP 32000 "some message" ]] means show "some message" until T 1 is reached. If you play the pattern it will very quickly flash the first message (for one generation).

Thirdly there's clearly some bug with Waypoints and STEP sizes. I won't be able to look at this until the weekend. Many thanks for the report.

Posted: **April 28th, 2022, 4:34 am**

Build 710 is now available on the lazyslug server

Fixes in this build:

fixed Population Graph screenshot height

Posted: **April 28th, 2022, 4:34 am**

Build 711 is now available on the lazyslug server

Fixes in this build:

enforce [[ WIDTH ]] and [[ HEIGHT ]] limits

Posted: **April 28th, 2022, 4:35 am**

Build 712 is now available on the lazyslug server

Fixes in this build:

fixed died generation

Posted: **April 30th, 2022, 1:07 pm**

Build 713 is now available on the lazyslug server

Fixes in this build:

[[ STOP ]] will now always define initial stop generation unless specified at a POI
fixed Waypoint target when playback throttled

Posted: **April 30th, 2022, 1:10 pm**

dvgrn wrote: April 24th, 2022, 4:24 pm Just ran into an oddity of the message-display system, maybe related to big step sizes or larger T values?

This should be fixed now. Also you can now put the [[ STOP ]] command anywhere you like except for in a POI definition.

Posted: **May 1st, 2022, 3:23 am**

Note that Themes with no history run much faster than those with history. For example in your pattern above if you set the THEME to Mono (a no history theme) for the first set of generations it will get to the "interesting" part much faster.

Code: Select all

x = 15926, y = 16272, rule = B3/S23
2bo$obo$b2o542$132bo$133bo$131b3o290$135b2o$134bobo$136bo$431b2o$430b
2o$432bo17$105bo$105b2o$104bobo7497$15923bobo$15923b2o$15924bo17$8105b
o$8106b2o$8105b2o$15893bo$15893bobo$15893b2o7448$99bobo$100b2o$100bo
17$427bo$425b2o$426b2o$131bo$129bobo$130b2o90$481bobo$481b2o$482bo198$
126b3o$128bo$127bo18$15896b3o$15896bo$15897bo74$478b3o$478bo$479bo$
187b2o$186bobo$188bo25$501b2o$500b2o$502bo!
#C [[ MAXGRIDSIZE 14 STEP 64 THEME Mono ]]
#C [[ STOP 32000 "Glider streams heading for epicentre" ]]
#C [[ T 40430 PAUSE 5 "Bit-Reading Glider #1 heading for SE GPSE" THEME Blues ]]
#C [[ T 48380 PAUSE 5 "'1' signal heading NE to epicentre" ]]
#C [[ T 52390 PAUSE 5 "Bit-Reading Glider #2 heading for SE GPSE" ]]
#C [[ T 56170 PAUSE 5 "'2' signal heading NE to epicentre" ]]
#C [[ T 58120 PAUSE 5 "Bit-Reading Glider #3 heading for SE GPSE" ]]
#C [[ T 60660 PAUSE 5 "'1' signal heading NE to epicentre" ]]
#C [[ T 61610 PAUSE 5 "Bit-Reading Glider #4 heading for SE GPSE" ]]
#C [[ T 62200 PAUSE 5 "'1' signal heading NE to epicentre" ]]

Posted: **May 15th, 2022, 3:52 pm**

Build 714 is now available on the lazyslug server

Fixes in this build:

fixed an issue with Advance Selection when all cells die in selection

ConwayLife.com

Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing

Re: Life tag testing