ConwayLife.com

Posted: **August 17th, 2021, 7:22 am**

rowett wrote: ↑
August 17th, 2021, 6:06 am
ColorfulGabrielsp138 wrote: ↑
August 17th, 2021, 5:46 am
I tried to post a troll, but failed.
Code: Select all
x = 0, y = 0, rule = R1,C2,S2,4-7,10,12-13,18-19,21,27,B2,5-7,11,13,15,19,21,27,NW010903090009030901
2o$2o$$3b2o$3b2o!
I suspect your State Weights are incorrectly specified. When you're using single hex digits to specify a weight then 8 to f represent 0 to -7. So where you have the digit 9 it means -1.

Use pairs of hex digits if you want values greater than 7.

See here for more information.

It worked! Thanks! But will it ever support triple or even more hex digits?

Code: Select all

x = 31, y = 5, rule = R1,C2,S2,4-7,10,12-13,18-19,21,27,B2,5-7,11,13,15,19,21,27,NW010903090009030901
bo7b2o6b2o7b2o$3o6bobo5bobo6bo2bo$bo10bo$13bo5bobo5bo2bo$12b2o6b2o7b2o!

Posted: **August 17th, 2021, 6:58 pm**

rowett wrote: ↑
August 15th, 2021, 11:47 am

muzik wrote: ↑
August 15th, 2021, 7:00 am
Is there any reason in specific why generation counts use a 64-bit float?
JavaScript.

So I assume the only data type for numbers is a 64-bit float, and there are no natively supported integer-only or such data types?

----

New bug: Fast Identify causes this to die at the world border, reporting a period-2 oscillator which does not seem to exist and history cells that never fade:

Code: Select all

x = 0, y = 0, rule = B2-a3-eiry4t5eijkn6-i/S1c2n3ekqy4eyz5-acy6-i78
3bo2b2o$4b2o2bo$2b7o$8obo$2b7o$o3b2o2bo$2b2o2b2o!
[[ THEME Blues ZOOM 1.0 ]]

Posted: **August 17th, 2021, 8:25 pm**

muzik wrote: ↑
August 17th, 2021, 6:58 pm
So I assume the only data type for numbers is a 64-bit float, and there are no natively supported integer-only or such data types?

There are two - Number and BigInt (infinite-length integer); BigInt is relatively new and for compatibility with older browsers like Internet Explorer, which nobody uses, you'll want to stick with Number.

(Also, NaN is a Number.)

Posted: **August 18th, 2021, 12:03 am**

LifeWiki article on LifeHistory wrote: State 5: start alive; enters state 4 upon death, and will never reappear during evolution.

Code: Select all

x = 5, y = 5, rule = LifeHistory
.A$2.A$3A2$4.E!
[[ AUTOSTART GPS 8 T 0 PAUSE 1 T 4 PAUSE 1 T 8 PAUSE 0.5 LOOP 30 ]]

-------------

muzik wrote: ↑
August 17th, 2021, 6:58 pm
New bug: Fast Identify causes this to die at the world border, reporting a period-2 oscillator which does not seem to exist and history cells that never fade:
Code: Select all
x = 0, y = 0, rule = B2-a3-eiry4t5eijkn6-i/S1c2n3ekqy4eyz5-acy6-i78
3bo2b2o$4b2o2bo$2b7o$8obo$2b7o$o3b2o2bo$2b2o2b2o!
[[ THEME Blues ZOOM 1.0 ]]

It also sometimes causes the pattern to die at ~500 or ~1000 generations, and also creates non-fading history cells.

Posted: **August 18th, 2021, 12:52 am**

pzq_alex wrote: ↑
August 18th, 2021, 12:03 am

LifeWiki article on LifeHistory wrote: State 5: start alive; enters state 4 upon death, and will never reappear during evolution.
Code: Select all
x = 5, y = 5, rule = LifeHistory
.A$2.A$3A2$4.E!
[[ AUTOSTART GPS 8 T 0 PAUSE 1 T 4 PAUSE 1 T 8 PAUSE 0.5 LOOP 30 ]]

yes this is intentional move on

Posted: **August 18th, 2021, 3:49 pm**

muzik wrote: ↑
August 17th, 2021, 6:58 pm
Fast Identify causes this to die at the world border, reporting a period-2 oscillator which does not seem to exist and history cells that never fade:

Fixed, thanks for reporting!

Posted: **August 19th, 2021, 3:14 am**

LifeViewer says "1 births" instead of "1 birth"

Posted: **August 20th, 2021, 12:16 pm**

bubblegum wrote: ↑
August 17th, 2021, 8:25 pm

muzik wrote: ↑
August 17th, 2021, 6:58 pm
So I assume the only data type for numbers is a 64-bit float, and there are no natively supported integer-only or such data types?
There are two - Number and BigInt (infinite-length integer); BigInt is relatively new and for compatibility with older browsers like Internet Explorer, which nobody uses, you'll want to stick with Number.

That's weird, because this following overflow implies the existence of some sort of 32-bit integer data type:

Code: Select all

x = 2, y = 8, rule = B3/S23
bo$o$bo$bo$bo$bo$bo$bo!
[[ HISTORYSTATES 4294967359 ]]

Code: Select all

x = 2, y = 8, rule = B3/S23
bo$o$bo$bo$bo$bo$bo$bo!
[[ HISTORYSTATES 4294967296 ]]

Code: Select all

x = 2, y = 8, rule = B3/S23
bo$o$bo$bo$bo$bo$bo$bo!
[[ HISTORYSTATES 4294967298 ]]

Posted: **August 20th, 2021, 12:44 pm**

I'm not sure if this is intended but it's quite irritating: for patterns with reversestart, the reset button (after some amount of playback first) will set them to forward playing on the first press.

Code: Select all

x = 3, y = 3, rule = MargSingRot
13o!
[[ REVERSESTART ]]

Compare:

Code: Select all

x = 3, y = 3, rule = MargSingRot
13o!

Posted: **August 20th, 2021, 3:54 pm**

muzik wrote: ↑
August 20th, 2021, 12:16 pm
That's weird, because this following overflow implies the existence of some sort of 32-bit integer data type:

Interesting - Number cannot overflow, as any number larger than about 1.8×10^38 is rounded up to Infinity. Additionally, no numeric types built-in to JavaScript are signed.

However, some operations, such as >>> (zero-fill right shift) and Array.prototype.length return unsigned 32-bit integers only, so the culprit might be one of those used on the value - or maybe LifeViewer is only reading a u32.

Posted: **August 20th, 2021, 4:29 pm**

bubblegum wrote: ↑
August 20th, 2021, 3:54 pm

muzik wrote: ↑
August 20th, 2021, 12:16 pm
That's weird, because this following overflow implies the existence of some sort of 32-bit integer data type:
However, some operations, such as >>> (zero-fill right shift) and Array.prototype.length return unsigned 32-bit integers only, so the culprit might be one of those used on the value - or maybe LifeViewer is only reading a u32.

Javascript supports Typed Arrays. In this case LifeViewer's script parser is storing parsed numeric arguments in a Uint32Array.

Posted: **August 21st, 2021, 3:21 am**

muzik wrote: ↑
August 20th, 2021, 12:44 pm
I'm not sure if this is intended but it's quite irritating: for patterns with reversestart, the reset button (after some amount of playback first) will set them to forward playing on the first press.

Fixed, thanks for reporting!

Posted: **August 24th, 2021, 10:45 am**

LV seems to sometimes just choose whatever it wants for gens/frame if that is set high enough, even if it is set differently. With the pattern here, setting it to 28 gens/frame, even at 1 fps, seems to give a completely random real gens/frame.

Posted: **August 24th, 2021, 11:03 am**

AforAmpere wrote: ↑
August 24th, 2021, 10:45 am
LV seems to sometimes just choose whatever it wants for gens/frame if that is set high enough, even if it is set differently. With the pattern here, setting it to 28 gens/frame, even at 1 fps, seems to give a completely random real gens/frame.

It's because by default LifeViewer will throttle playback if updates are taking too long to ensure responsiveness.

You can disable performance throttling with Settings->Playback->Throttle.

Posted: **August 24th, 2021, 12:12 pm**

Is the reset button supposed to appear usable even in cases where it wouldn't do anything?

Posted: **August 24th, 2021, 1:18 pm**

muzik wrote: ↑
August 24th, 2021, 12:12 pm
Is the reset button supposed to appear usable even in cases where it wouldn't do anything?

Yes

Posted: **August 31st, 2021, 10:43 am**

Could warnings of some sort be added to functions which aren't yet fully supported (e.g. Identify on Margolus, Identify on hexagonal/triangular rules pertaining to missing parameters, and selections and rotation/flipping of said selections in hexagonal/triangular rules) to indicate that they're not yet fully developed and to clarify that unexpected behaviour may arise as a result?

Posted: **August 31st, 2021, 11:32 am**

Is TRACK limited intentionally? It seems a bit overly restrictive, and prevents the comfortable tracking of faster-than-light patterns. I assume these restrictions were put in place before higher range rule support?

Code: Select all

x = 0, y = 0, rule = B3/S23
!
#C [[ TRACK 2 2 PASTEMODE 6 PASTEDELTA 2 2 PASTET EVERY 1 0 16384 PASTE
71b2o$72bo$72b2o$73bo$73b2o$74bo$74b2o$75bo$75bo$75bo$76bo$76bo$76bo$
76bo$76bo$76bo$76bo$76bo$76bo$76bo$76bo$76bo$75bo$75bo$75bo$74bo$74bo$
73bo$72b2o$71bo$70bo$69bo$67b2o$65b2o$64bo$62b2o$61bo$59b2o$57b2o$55b
2o$53b2o$52bo$50b2o$48b2o$45b3o$43b2o$39b4o$37b2o$o33b3o$b2o29b2o$3bo
23b5o$4b2o14b7o$6b14o! ]]

Code: Select all

x = 0, y = 0, rule = B3/S23
!
#C [[ TRACK 3 3 PASTEMODE 6 PASTEDELTA 3 3 PASTET EVERY 1 0 16384 PASTE
71b2o$72bo$72b2o$73bo$73b2o$74bo$74b2o$75bo$75bo$75bo$76bo$76bo$76bo$
76bo$76bo$76bo$76bo$76bo$76bo$76bo$76bo$76bo$75bo$75bo$75bo$74bo$74bo$
73bo$72b2o$71bo$70bo$69bo$67b2o$65b2o$64bo$62b2o$61bo$59b2o$57b2o$55b
2o$53b2o$52bo$50b2o$48b2o$45b3o$43b2o$39b4o$37b2o$o33b3o$b2o29b2o$3bo
23b5o$4b2o14b7o$6b14o! ]]

Also, not sure if this is a bug or not, but within the region that gets pasted over, all history cells are replaced with was-always-dead cells and all alive cells are replaced with newly born looking cells, but the pattern behaviour remains overall unchanged:

Code: Select all

x = 0, y = 0, rule = B3/S23
!
#C [[ TRACK 0.5 0 PASTEMODE 6 PASTEDELTA 1 0 PASTET EVERY 2 0 16384 PASTE
71b2o$72bo$72b2o$73bo$73b2o$74bo$74b2o$75bo$75bo$75bo$76bo$76bo$76bo$
76bo$76bo$76bo$76bo$76bo$76bo$76bo$76bo$76bo$75bo$75bo$75bo$74bo$74bo$
73bo$72b2o$71bo$70bo$69bo$67b2o$65b2o$64bo$62b2o$61bo$59b2o$57b2o$55b
2o$53b2o$52bo$50b2o$48b2o$45b3o$43b2o$39b4o$37b2o$o33b3o$b2o29b2o$3bo
23b5o$4b2o14b7o$6b14o! ]]

Posted: **August 31st, 2021, 9:27 pm**

When using a script blocker such as NoScript or uBlock on pages with embedded viewers (e.g., here or here), the viewer doesn't appear, but there is a large blank area where the viewer would be. It seems that the canvas element is still being produced, but it can't be drawn on by LifeViewer. If I disable javascript directly in the browser using debugging options, the canvas doesn't seem to be created, and there's no large blank area.

The reason I bring this up is that I want to replace the images in the Lifeline wiki articles with LifeViewer thumbnails, but I would like the images to still appear if JavaScript is disabled. The wiki template LV:Viewer is used to embed the viewer on wiki pages, and it has an option to replace the viewer with specified content when JavaScript is disabled, but due to the reasons stated above, it doesn't work with script blockers.

I consider this a low priority, but if the fix is easy, I would appreciate it. I tried a few things on the wiki, but I wasn't able to get the desired behavior.

Edit: extremely low-priority request: have camera angle work for hexagonal and triangular grids.

Posted: **September 1st, 2021, 4:27 am**

Sokwe wrote: ↑
August 31st, 2021, 9:27 pm
When using a script blocker such as NoScript or uBlock on pages with embedded viewers (e.g., here or here), the viewer doesn't appear, but there is a large blank area where the viewer would be. It seems that the canvas element is still being produced, but it can't be drawn on by LifeViewer. If I disable javascript directly in the browser using debugging options, the canvas doesn't seem to be created, and there's no large blank area.

Short answer: not sure there's anything I can do about it.

Detail:
LifeViewer uses an HTML5 <canvas> element for the display.

For example:

Code: Select all

<canvas width="640" height="520"></canvas>

will create a 640x520 canvas.

The <canvas> element requires Javascript for drawing.

If Javascript is disabled in the browser then the <canvas> is not displayed, and instead any text defined in the <canvas> element is displayed:

Code: Select all

<canvas width="640" height="520">Please enable Javascript to see the canvas!</canvas>

However, if you're using NoScript or uBlock they use Content-Security-Policy HTTP headers to tell the browser it's not allowed to load Javascript. In this case Javascript is enabled in the browser, but the security policy blocks the browser from loading it. So the <canvas> is displayed (since Javascript is enabled) but LifeViewer can't run since it was blocked from loading.

Sokwe wrote: ↑
August 31st, 2021, 9:27 pm
Edit: extremely low-priority request: have camera angle work for hexagonal and triangular grids.

Thanks for the request - it's highly unlikely.

Posted: **September 1st, 2021, 10:23 am**

muzik wrote: ↑
August 31st, 2021, 11:32 am
Is TRACK limited intentionally? It seems a bit overly restrictive, and prevents the comfortable tracking of faster-than-light patterns. I assume these restrictions were put in place before higher range rule support?

I will extend the allowed range in a future build.

Posted: **September 1st, 2021, 12:34 pm**

rowett wrote: ↑
September 1st, 2021, 4:27 am
However, if you're using NoScript or uBlock they use Content-Security-Policy HTTP headers to tell the browser it's not allowed to load Javascript. In this case Javascript is enabled in the browser, but the security policy blocks the browser from loading it. So the <canvas> is displayed (since Javascript is enabled) but LifeViewer can't run since it was blocked from loading.

Thanks for the info. Would it be possible (or reasonable) to create the canvas element dynamically with JavaScript, so that it won't be created if JavaScript is disabled? Again, this is low-priority, since I doubt there are many people who would use this site with script-blockers anyway.

Posted: **September 2nd, 2021, 3:51 pm**

Sokwe wrote: ↑
September 1st, 2021, 12:34 pm
Would it be possible (or reasonable) to create the canvas element dynamically with JavaScript, so that it won't be created if JavaScript is disabled?

Yes it's possible. It will need coordination with Nathaniel since the templates that generate the embedded viewers here on the forum and Wiki will need to change. I'll put it on the backlog.

Posted: **October 18th, 2021, 8:18 pm**

Can Identify report the generation in which a pattern died in the same way it does with normal playback?

Code: Select all

x = 8, y = 3, rule = B3/S23
bo$6bo$3o3b2o!

Also, when using Identify or HistoryFit, the pattern seems to zoom out a lot at the end, much more than would be expected.

Posted: **October 21st, 2021, 10:13 pm**

@ rowett :

Code: Select all

x = 721, y = 512, rule = B3/S23
15b2o$15b2o5$265b2o16bo$265b2o16bo$283bo$290b2o59b2o$279b3o3b3o2b2o59b
2o$2b2o$2b2o279bo$283bo$283bo$10b2o$2b3o5b2o$252b2o32b2o72b2o$o5bo245b
2o32b2o72b2o$o5bo$o5bo17b2o16b2o16b2o16b2o16b2o16b2o16b2o204b2o$23bobo
15bobo15bobo15bobo15bobo15bobo15bobo126b2o76b2o$2b3o247b3o5b2o39b2o$
21bobo15bobo15bobo15bobo15bobo15bobo15bobo169b2o$21b2o16b2o16b2o16b2o
16b2o16b2o16b2o11bo107bo5bo89b2o$141bobo97b2o7bo5bo81b3o5b2o$141bo2bo
96b2o7bo5bo$142b2obo190bo5bo$144bobo71b2o32b3o81bo5bo30b2o$144bo2bo70b
2o116bo5bo30b2o$145b2o$338b3o$365b2o$365b2o5b3o2$370bo5bo$228b2o140bo
5bo$228b2o140bo5bo2$205b2o165b3o$205b2o22bo6b2o$229bo6b2o$229bo$213b2o
$205b3o5b2o10b3o3b3o$148b2o$147bobo53bo5bo19bo$203bo5bo19bo$145bobo55b
o5bo19bo$145b2o$205b3o226b2o$358b2o74b2o$358b2o2$163bobo$164b2o$164bo
3$407b3o2$405bo5bo3b2o30b2o$405bo5bo3b2o30b2o$148b2o255bo5bo$147bobo$
407b3o29b2o$145bobo291b2o5b3o$145b2o$444bo5bo$411b2o31bo5bo$411b2o31bo
5bo$469b2o$446b3o20b2o2$426b2o$426b2o6$148b2o$147bobo60b2o270b2o$186b
2o22b2o270b2o$145bobo38b2o$145b2o267b2o$414bo59b2o6bo$412bobo59b2o6bo$
412b2o68bo2$478b3o3b3o2$482bo$482bo$482bo5$148b2o$147bobo2$145bobo$
145b2o345b2o$189b2o301b2o$189b2o2$481b2o$481bo$479bobo$479b2o4$505b2o$
176b2o327b2o$176b2o$148b2o$147bobo347b2o$184b2o311b2o5b3o$145bobo28b3o
5b2o$145b2o355bo5bo$174bo5bo321bo5bo$174bo5bo321bo5bo$174bo5bo$504b3o$
176b3o9$148b2o$147bobo2$145bobo$145b2o7$495b2o$495b2o6$148b2o$147bobo
2$145bobo$145b2o7bo353b2o$154bo353b2o$154bo325b2o$480bo$150b3o3b3o319b
obo19b2o6bo$478b2o20b2o6bo$154bo353bo$154bo6b2o$154bo6b2o341b3o3b3o2$
508bo$153b2o353bo$153b2o353bo3$178b2o$178b2o6$166b2o$166b2o49$516b3o2$
514bo5bo$514bo5bo$514bo5bo2$509b2o5b3o$509b2o$185b2o$185b2o$517b2o$
517b2o6$149b3o2$147bo5bo18b2o$147bo5bo18b2o$147bo5bo350b2o$504b2o$149b
3o5b2o14bo6b2o$157b2o14bo6b2o$173bo2$149b2o18b3o3b3o$149b2o$173bo$173b
o$173bo7$162b2o$162b2o17$163b3o2$161bo5bo$161bo5bo$161bo5bo2$163b3o5b
2o$171b2o3$163b2o$163b2o10$176b2o$176b2o7$184b3o2$182bo5bo$182bo5bo$
182bo5bo2$184b3o5b2o$192b2o3$184b2o$184b2o$218b2o$218b2o8$197b2o$197b
2o11$418bo$418bo$418bo2$414b3o3b3o$242b3o$418bo$156b3o81bo5bo163b2o6bo
154b2o$240bo5bo163b2o6bo155bo$154bo5bo79bo5bo324bobo$154bo5bo409bo$
154bo5bo81b3o5b2o166b2o150b2o$250b2o166b2o$156b3o5b2o$164b2o$242b2o$
242b2o$156b2o$156b2o4$405b2o$405b2o$379b3o$573b2o$255b2o71bo48bo5bo71b
2o117bo$255b2o71bo48bo5bo71b2o114bobo$169b2o157bo48bo5bo186bo$169b2o
399b2o$324b3o3b3o39b2o5b3o$372b2o$328bo$328bo6b2o97b3o$328bo6b2o43b2o$
380b2o50bo5bo$432bo5bo$327b2o103bo5bo$327b2o$427b2o5b3o$427b2o3$435b2o
136b2o$435b2o137bo$367b2o202bobo$367b2o201bo$570b2o$340b2o$340b2o5$
422b2o$422b2o6$573b2o$574bo$571bobo$570bo$570b2o14$573b2o$574bo$571bob
o$570bo$570b2o14$552b3o18b2o$552bo21bo$553bo17bobo$570bo$570b2o2$552b
2o$551b2o$547b2o4bo$163bo382b2o$163b2o383bo$162bobo7$573b2o$574bo$571b
obo$570bo$570b2o15$573b2o$572bo2bo$573bobo$574bob2o$575bo2bo$576bobo$
577bo11b2o16b2o16b2o16b2o16b2o16b2o16b2o$590bo17bo17bo17bo17bo17bo17bo
17bo$587bobo15bobo15bobo15bobo15bobo15bobo15bobo18bo$586bo17bo17bo17bo
17bo17bo17bo21bo$586b2o16b2o16b2o16b2o16b2o16b2o16b2o$712b3o3b3o2$716b
o$708b2o6bo$708b2o6bo3$716b2o$716b2o10$703b2o$703b2o!

Here is my "showy" version of Rabbits you may want to use to Show Off your EXCELLENT Web Page Life Viewer !

I call it Rabbits in a Pulsar Containment Field or, alternatively, Viro and four of his Friends get together for some Recreational Procreation !

Thank You !

Cheers !

ConwayLife.com

Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads