ConwayLife.com

rowett wrote:Correct, LtL is not yet complete in LifeViewer.

rowett wrote:Hopefully in a few weeks. I've been busy.

Electro_blob wrote:How exactly do you make patterns in this thing?

.......*.
.**..*.*.
*..*..**.
.*.*.....
..*......
........*
......***
.....*...
.....**..

.OO..O.OO
O..O..OO.
.O.O.....
..O......
........O
......OOO
.....O...
......O..
.......OO

Electro_blob wrote:Thank you allot. I think I'm starting to understand. Why are there $'s and numbers... if it is just binary?

Electro_blob wrote:Thank you allot. I think I'm starting to understand. Why are there $'s and numbers? For example in,

Code: Select all

x = 9, y = 9, rule = B3/S23
b2o2bob2o$o2bo2b2o$bobo$2bo$8bo$6b3o$5bo$6bo$7b2o!
#C [[ AUTOSTART GPS 7 TRACK -1/7 0 THUMBNAIL GRID THEME 4 ]]

if it is just binary?

lifeisawesome wrote:11-59 fps is actually 10 fps, slowly increasing to 20 fps.

wildmyron wrote:There's a bug in LifeViewer's handling of negative coord values in #CXRLE lines for rules on bounded grids.

wildmyron wrote:Panning would be much more useful if the step was zoom dependent.

rowett wrote:When you set the fps you are setting the target fps. The actual fps will depend on the power of your computer and the complexity and size of the pattern. If LifeViewer can't meet the target it will draw the fps background in red.

77topaz wrote:

rowett wrote:When you set the fps you are setting the target fps. The actual fps will depend on the power of your computer and the complexity and size of the pattern. If LifeViewer can't meet the target it will draw the fps background in red.

When I use LifeViewer, it behaves slightly differently: the background of the FPS box is always red when a pattern is running, even at just 1 FPS. However, at large step sizes for complex patterns that the system can't seem to keep up with, I see the background of the step size box flashing.

• improved POI capability
  • you can now specify any of the following settings at each POI
    • [[ X Y ZOOM ANGLE LAYERS DEPTH GPS STEP THEME LOOP STOP ]]
  • you can also specify actions at each POI
    • [[ POIRESET ]] - reset playback to T = 0
    • [[ POIPLAY ]] - continue playback from current generation
    • [[ POISTOP ]] - pause playback
    • [[ POIT <generation> ]] - skip to defined generation
  • [[ POITRANS 0..200 ]] specifies the transition speed to the POI in frames (1/60ths of a second)
    • 0 means instantaneous transition
    • if not specified then the default is 12
  • a POI will only change the settings that are defined and other settings are left unmodified
  • the initial settings are the default settings for LifeViewer and can be overridden with script commands before any POI definition
  • added script keyword [[ INITIAL ]] that can be used in a POI definition
    • [[ ALL INITIAL ]] makes all settings for the POI the same as the initial settings
      • the required settings can then be overridden e.g. [[ POI ALL INITIAL ZOOM 4 ]] copies all and overrides ZOOM
    • [[ X|Y|ZOOM|ANGLE|LAYERS|DEPTH|GPS|STEP|THEME|LOOP|STOP INITIAL ]] copies the initial setting of the defined parameter into the POI
      • [[ POI X INITIAL Y INITIAL ]] sets X and Y from the initial and leaves everything else unchanged
    • [[ POI INITIAL ]] makes the defined POI the default on pattern load rather than the initial settings (note this does not change the initial settings for copying)
• Pattern decoders
  • added support for Hex and von Neumann neighbourhoods to MAP rules
  • MAP rules now allow base64 padding
  • Life 1.05 format patterns now support all rules including bounded grids
• Script commands
  • new script command [[ SUPPRESS ]] which suppresses overwrite error message for duplicate definitions once
  • [[ WIDTH ]] and [[ HEIGHT ]] are now checked for duplicate definitions
  • [[ STOP ]] and [[ LOOP ]] can now take the parameter [[ OFF ]] to disable them (useful for POI definitions)
  • [[ STOP ]] and [[ LOOP ]] tooltips now show generation
  • [[ NOSOURCE ]] now also hides the "CODE : SELECT ALL" line on the forum
• UI
  • hotkeys alt and "1" to alt and "9" will switch to respective POIs (if defined)
  • hotkey shift and "c" now cycles backwards through colour Themes
  • hotkey alt and "c" selects the default Theme
  • panning with the cursor keys is faster when zoomed out
  • hotkey shift and "l" will toggle LOOP mode if defined
  • help information now marks current POI with *
• General
  • whitespace at the beginning of lines is now removed before copying patterns to the clipboard

• Pattern decoders
  • rules in the format SnnBnn were being decoded with S and B transposed
  • non-totalistic rules with repeated neighbour counts were decoded incorrectly
  • bounded grids were not working correctly with CXRLE POS
• UI
  • copy pattern source (hotkey "c") was not working correctly in the standalone Viewer
  • LifeHistory patterns were not respecting Themes at generation 0
  • updated event handling for the UI to handle spurious mouseleave events posted when both mouseup and mousedown happen between updates
  • if there were more script errors than could fit on one page of the Viewer then the last error could not be scrolled to
  • LOOP was performing a camera reset when LOOP enabled after the LOOP generation
• General
  • Waypoint error messages were showing incorrect sign when overwriting X or Y camera positions
  • an error could be generated about XOFFSET and YOFFSET when they weren't specified

Saka wrote:So no LTL yet?

rowett wrote:

Saka wrote:So no LTL yet?

No, it's not finished yet. LTL patterns get successfully decoded and validated. I just haven't finished the runtime. And no, I'm not sure how long that will take.

Thanks for asking

• fixed LifeHistory states 2 and 6 that were broken by the previous release

rowett wrote:Build 239 is now live on the Forums and LifeWiki

Please note: you will need to refresh your browser to use the new build

Fixes since the last released build:

• fixed LifeHistory states 2 and 6 that were broken by the previous release

Comments, feedback, suggestions and bug reports welcome!

77topaz wrote:I'm getting some slightly annoying behaviour that I didn't get previously: when I drag the GPS or x sliders, and I drag one all the way to the end so my mouse cursor ends up above the other slider, it automatically selects that slider when I release my mouse, which means I keep adjusting the GPS unintentionally while changing the x, and vice versa.

rowett wrote:Thanks for reporting!

I believe I have fixed the issue.

Please test it here and let me know if it's working as you expect.
You may need to refresh your browser on the test page to get the new build. Click the Help button on the Viewer and it should say Build 240.

fluffykitty wrote:Bug: 60gps is a lot faster than 59gps.