ConwayLife.com

muzik wrote:I want to know, when will the next update for the mobile version come out?

Scorbie wrote:Almost all golly scripts convert golly's cell lists to list of cell coordinates.

That's why there are posts saying "You can do it with zip(celllist[::2], celllist[1::2]) in Python!" in the scripts thread.
I haven't used Lua, so I am not sure what is the best practice to achieve the same thing. Does anybody know this?

local g = golly()

local function zip(cellarray)
    -- convert one-state cell array: { x1, y1, x2, y2, ... xn, yn }
    -- to array of cell coordinates: { {x1,y1}, {x2,y2}, ... {xn,yn} }
    if (#cellarray & 1) == 1 then
        -- cellarray has an odd number of ints
        g.exit("Given cell array is multi-state.")
    end
    local coords = {}
    for i = 1, #cellarray, 2 do
        coords[#coords + 1] = { cellarray[i], cellarray[i+1] }
    end
    return coords
end

local carray = g.getcells(g.getrect())
local coords = zip(carray)

g.note(carray[1]..","..carray[2])         -- displays x1,y1
g.note(coords[1][1]..","..coords[1][2])   -- ditto

Andrew wrote:I'm assuming you mean all the scripts you write? I've never found the need to do that.

muzik wrote:This has more than likely been asked before, but will there ever be support for non-totalistic rules in Golly without having to generate a rule table? LifeViewer is capable of this:

Code: Select all

x = 5, y = 3, rule = B36_S2-i34q
5o$5o$5o!

Scorbie wrote:This was asked before and Andrew's answer was "probably no, we have other priorities."

muzik wrote:

Scorbie wrote:This was asked before and Andrew's answer was "probably no, we have other priorities."

What are said priorities?

dvgrn wrote: The biggest change for Golly 2.8 is Lua support, which will make it possible to run scripts without a separate Perl or Python install, or the attendant versioning and 32-vs-64-bit headaches. Personally I'm hoping to get some significant updates in for the Life Lexicon and the pattern collection as well, though here it is June already and those projects aren't exactly done yet.

That said, I think the "probably no" has been adjusted to something a bit more positive recently. Not to name any names or make promises on anyone else's behalf, but at least we have a new potential contributor who is looking at adding the necessary code for native isotropic rule support. Check the golly-test list on Sourceforge for details...!

muzik wrote:Wait. Chris is the developer of LifeViewer, right?

local g = golly()
local gp = require "gplus"

local orig = gp.pattern("2o!") -- domino
local temp = orig[10] -- temp is empy, but...

g.exit(#orig) -- orig is empty too?!!

import golly as g
import glife

orig = glife.pattern("2o!") # Domino
temp = orig[10]

g.exit(str(orig)) # Cell list of a domino, as expected.

Scorbie wrote:Is it intended behavior for indexing in gplus to change the original pattern?

g.exit(#orig.array)

muzik wrote:why are some named rules not listed on the scroll down thing on the mobile version?

Andrew wrote:

Scorbie wrote:Is it intended behavior for indexing in gplus to change the original pattern?

It doesn't. Lua's length operator (#) only returns sensible results for strings and for tables that use integer indices starting at 1. To get the length of the cell array stored in the table created by gp.pattern you have to do this:

Code: Select all

g.exit(#orig.array)

See the m.pattern function in Scripts/Lua/gplus/init.lua for details.

muzik wrote:Another question that has probably been asked a lot, but will Golly ever be able to simulate odd Wolfram rules?

biggiemac wrote:Ok just installed this, had been using 2.6. I'm not sure if I did something wrong regarding GollyPrefs before opening the new version but it doesn't seem to adapt to my 4K monitor, while 2.6 never had this problem. The infoboxes and toolbars are too small to reasonably use and I'm wondering what to change to fix this.

Andrew wrote:

biggiemac wrote:Ok just installed this, had been using 2.6. I'm not sure if I did something wrong regarding GollyPrefs before opening the new version but it doesn't seem to adapt to my 4K monitor, while 2.6 never had this problem. The infoboxes and toolbars are too small to reasonably use and I'm wondering what to change to fix this.

More details please. Is this on Windows, Mac or Linux? 64-bit or 32-bit? More technical info on your monitor would be handy. A screenshot would be even more useful (especially one comparing 2.6 with 2.8b3).

biggiemac wrote:Windows 10, 64-bit golly on 64-bit OS, N501VW Asus laptop.
Screenshots of 2.6 and of 2.8b3 upon launch.

biggiemac wrote:The scaling problem has been fixed, thanks!

The Python scripts crash the same as before. ...

Andrew wrote:I see in another thread that you installed Python 2.7.11. There is a known bug with that version, so you need to uninstall it, then download and install an earlier version like 2.7.10 (64-bit of course).