ConwayLife.com

NNlk05 wrote: June 30th, 2026, 2:37 am

aengmore wrote: June 29th, 2026, 10:12 pm I try to use the Windows version on my phone, and it failed
*snip*

Since Android is a version of Linux, maybe running the Linux version will be smoother.

Well, maybe I can try using Termux to run Linux version……but apparently it will be much more troublesome, probably with more technological difficulties and bugs

For some reason, when I use nbsearch2a and stop it all the cells are in this weird greyed-out state that counts as dead:

NNlk05 wrote: September 5th, 2026, 1:08 pm For some reason, when I use nbsearch2a and stop it all the cells are in this weird greyed-out state that counts as dead:

Looks like new layer was created. I suggest to try clicking Layer -> Delete Layer.

I have a particularly major problem relating to Golly 1.5 for iPadOS: opening selection boxes at all (for attempting to paste a pattern into Golly, for selecting a pattern in an attempt to copy/clear/random fill (as the attachment demonstrates. In this, I am one tap away from crashing Golly by trying to copy the pattern), or selecting which copy method to use... but curiously NOT the menu that appears on overwriting an already existing saved file) crashes Golly consistently on iPadOS 27. This is serious enough that I have to bring this to attention immediately.

I've updated my iPad to iOS 27 and can reproduce the paste crash. There are other crashes as well so I'll try to fix those soon and release a new version. Thanks for the report.

I am not sure if this is intentional, but files with no extension cannot be viewed in the Files panel (this previously lead to the assumption that one of my files was deleted):

qqd wrote: September 18th, 2026, 2:30 am I am not sure if this is intentional, but files with no extension cannot be viewed in the Files panel ...

Must be a Windows quirk because I definitely see such files on macOS. Golly's code says to display all files.

web golly throws errors in console when webgl is disabled
maybe some kind of graceful alert to the user would be good? "webgl is required" or smth

While using a ruleloader rule, if you increase n_states, when Golly tries to update to the newly modified rule, all new states become broken and trying to click on one of them in the state selector will cause Golly to freeze. (Using MacOS)

I6_I6 wrote: October 10th, 2026, 4:16 am While using a ruleloader rule, if you increase n_states, when Golly tries to update to the newly modified rule, all new states become broken and trying to click on one of them in the state selector will cause Golly to freeze. (Using MacOS)

I can't reproduce any error so please describe in more details what steps you did. Maybe post the .rule data before and after the change. Here's what I did:

* Clicked on a .rule file containing @TABLE data with 10 states (so Golly loaded it).
* Ctrl-clicked on the file so it opened in my text editor.
* Increased n_states to 11 and appended "10 0 0 255" to the @COLORS section.
* Saved the changes and clicked on the .rule file again.
* Golly loaded the new rule and I could switch to the new state without any problems.

So what steps did you do?

Andrew wrote: October 11th, 2026, 7:33 am

I6_I6 wrote: October 10th, 2026, 4:16 am While using a ruleloader rule, if you increase n_states, when Golly tries to update to the newly modified rule, all new states become broken and trying to click on one of them in the state selector will cause Golly to freeze. (Using MacOS)

I can't reproduce any error so please describe in more details what steps you did. Maybe post the .rule data before and after the change. Here's what I did:

* Clicked on a .rule file containing @TABLE data with 10 states (so Golly loaded it).
* Ctrl-clicked on the file so it opened in my text editor.
* Increased n_states to 11 and appended "10 0 0 255" to the @COLORS section.
* Saved the changes and clicked on the .rule file again.
* Golly loaded the new rule and I could switch to the new state without any problems.

So what steps did you do?

Instead of clicking the .rule file again, I ran the pattern and then reset, which makes Golly reread the .rule file.

I6_I6 wrote: October 11th, 2026, 8:00 am Instead of clicking the .rule file again, I ran the pattern and then reset, which makes Golly reread the .rule file.

Ok, that let me reproduce the bug. I've fixed it for the next release (Golly 5.1b1) which will hopefully happen in a few days.

Depending on the changes you make to an active .rule file you might still get annoying warning messages, so I strongly recommend making changes at generation 0 or, even safer, when the .rule file is not the currently active rule.