Would it be possible to make LifeViewer throw an error if that happens?rowett wrote: March 29th, 2025, 3:27 pm [...]
The var q1={0,2,4,5} contains an illegal state. There are only 5 states n_states: 5 which are 0 to 4.
Code: Select all
#R name
!
[[ RANDOMIZE ]]
@RULE name
@TABLE
n_states:3
neighborhood:Moore
symmetries:rotate4reflect
var a={0,1,2}
var a1=a
var a2=a
var a3=a
var a4=a
var a5=a
var a6=a
var a7=a
var a8=a
0,3,0,0,0,0,0,0,0,1
Fixed in build 1300, thanks.dvgrn wrote: March 30th, 2025, 7:59 am Has TRACKLOOP stopped working, as of build 1299 or thereabouts?
Yes in build 1301, thanks.b-engine wrote: March 30th, 2025, 7:39 am LifeViewer throws an error if an invalid ruletable is provided, all because of "Unsupported rule name" despite the error actually being in ruletable. Could you make LifeViewer throw an accurate error?
confocaloid wrote: March 27th, 2025, 6:10 am At some point recently, LifeViewer selections began working in an unexpected way.
Fixed in build 1302, thanks.WhiteHawk wrote: March 31st, 2025, 3:26 am LifeHistory history cells are not "grabbable" anymore in the sense that when autoselect is chosen, the select box shrinks to the live/alternate cells, making it hard to measure bounding boxes.
When will it be implemented? Still having trouble grabbing history cellsrowett wrote: March 31st, 2025, 6:27 amconfocaloid wrote: March 27th, 2025, 6:10 am At some point recently, LifeViewer selections began working in an unexpected way.Fixed in build 1302, thanks.WhiteHawk wrote: March 31st, 2025, 3:26 am LifeHistory history cells are not "grabbable" anymore in the sense that when autoselect is chosen, the select box shrinks to the live/alternate cells, making it hard to measure bounding boxes.
It's already deployed. It can take up to 4 hours to appear.WhiteHawk wrote: March 31st, 2025, 7:02 am When will it be implemented? Still having trouble grabbing history cells
In build 1302:rowett wrote: March 31st, 2025, 6:27 am[...]confocaloid wrote: March 27th, 2025, 6:10 am At some point recently, LifeViewer selections began working in an unexpected way.
Fixed in build 1302, thanks.
Code: Select all
#C [[ HARDRESET STARTFROM 105 ]]
x = 27, y = 26, rule = LifeHistory
.A$2.A$3A19$25.2A$25.2A2$14.2A$14.2A!
Code: Select all
#C [[ STOP 105 ]]
x = 27, y = 26, rule = LifeHistory
.A$2.A$3A19$25.2A$25.2A2$14.2A$14.2A!
Code: Select all
#C [[ STOP 105 ]]
x = 27, y = 26, rule = B3/S23
bo$2bo$3o19$25b2o$25b2o2$14b2o$14b2o!
I see it now. Now how would it be fixed on Catagolue?
Fixed in build 1303, I hope. Thanks.confocaloid wrote: March 31st, 2025, 12:52 pm In the next example, "Select All" still works in an unexpected way (it selects a 28-by-28 region, while it should select a 30-by-30 region instead)
Catagolue updates itself on a different schedule. I guess once every 24 hours but I don't know for sure.
When viewed in scale <0, it disappears.islptng wrote: April 1st, 2025, 10:25 pmCode: Select all
x = 38, y = 29, rule = B3/S23 19bo2$14bobobob2o5bo$13bobo6b2o3bo$11b2o2b2o2b4o$8bo2b3o5bo4bo4b3o$3bo bo2b3o4b2o3bob5obo2bo$3b2o4bo8b2obobo4b2ob2o$4bo13b3o10b2o$o14bo4bo5bo 3bo3b2o$14bobo4bo4bo3bobo$o13bo6b2o3bo8bo$5bo9b2obo3bo3b3obo2b4o$4b2o 6bo5bo2b5ob4o2b2ob2o$4bobo11bob2o7bo5b2o$12bo4bo3bo4bobo$17bo2b2o4bobo $9b4obob2o2bob2o3bo$11b5o5b2o$11bo3b3o6bo4b3o$12b3o2b2o3b5obo2bo$12b3o 6bobo4b2ob2o$13b2o3b3o10b2o$15b2o3bo5bo3bo3b2o$15bo4b2o4bo3bobo$15bo3b 4o3bo8bo$18bo3bo3b3obo2b4o$21b5ob4o2b2ob2o$27bobo5b2o! [[ PASTET 1 PASTEMODE XOR PASTE 16b2o$11b2o5b2o$19b2o$10bo2bo4b2o7bo$5bo4bobob2o2bo2bo4b3o$o4bobo2b2o b3o3bo2bob2o$obo2b2o7bo2b2obobob3o$2o14b3o7bo2b2o$27bob2o$10b2o2bo2bo bo2b3o3bo2b2o$11bobobob3o2b2o2bobobob2o$b2o7b2o5bo3bo5bo2bo3bo$bobo14b 5o4bo2bo3bo$bo17b5o3bo3b4o$6b2o4bo2b2o8b2o$6bobo7b2o5bobo$6bo4bob2o2b ob2o3bo$11bo6b2o7bo$11b2ob2o2bo2bo4b3o$14b2o3bo2bob2o$14bo2b2obobob3o $12bo3b3o7bo2b2o$10b2o15bob2o$11bobo5bo2b3o3bo2b2o$12bo3bo2bo2b2o2bob obob2o$16bo4bo5bo2bo3bo$18b5o4bo2bo3bo$19b3ob2ob2o3b4o! 3 1 STARTFROM 1 THEME Mono ]]
I'm once again asking.
Threre's nothing else I can do at the moment. I can't reproduce it. I guessed at a fix and it didn't help.b-engine wrote: April 6th, 2025, 8:28 am I'm once again asking.
Please assign a high priority to this bug, even if you don't observe it.
Well, whatever are the specifications of the device you used to try reproduce this?rowett wrote: April 6th, 2025, 8:34 am There's nothing else I can do at the moment. I can't reproduce it. I guessed at a fix and it didn't help.
What do your two devices have in common?b-engine wrote: April 6th, 2025, 8:37 am This had happened in two devices, one running Android 14, and the other Android 9.
They are both mobile phones and have touchscreen. Results are obtained in Chrome - any version could reproduce this.
It's still build 1304 on my device, and there's no obvious way to hard refresh.
What make are both devices? It's something specific to your devices since no one else has reported this specific issue.b-engine wrote: April 6th, 2025, 9:53 am They are both mobile phones and have touchscreen. Results are obtained in Chrome - any version could reproduce this.
On Android devices there's typically a Clear Browsing Data option in Chrome settings.b-engine wrote: April 6th, 2025, 9:53 am It's still build 1304 on my device, and there's no obvious way to hard refresh.
They're from different brands, therefore it's not a brand specific issue.rowett wrote: April 6th, 2025, 10:06 am What make are both devices? It's something specific to your devices since no one else has reported this specific issue.
I cleared the browsing data, but the build remains as 1304.rowett wrote: April 6th, 2025, 10:06 am On Android devices there's typically a Clear Browsing Data option in Chrome settings.
Which brands are they? The more information you can give me the more likely we are to find a solution.b-engine wrote: April 6th, 2025, 10:11 am They're from different brands, therefore it's not a brand specific issue.
It can take up to 4 hours for new builds to appear on the forums. Try doing the same on the LifeViewer home page.
This bug would never occur in LifeViewer homepage or ConwayLife homepage. The only known occurrences happen in the forums or LifeWiki.rowett wrote: April 6th, 2025, 10:28 am It can take up to 4 hours for new builds to appear on the forums. Try doing the same on the LifeViewer home page.
rowett wrote: April 6th, 2025, 10:28 am Which brands are they? The more information you can give me the more likely we are to find a solution.
EDIT:b-engine wrote: December 7th, 2024, 7:05 am 1. Currently using Huawei P10+ (Is this old enough?)
2. Presumably Android 7.1
3. Chrome 131.0.6778.104
Which device and browser are you using?R2INT wrote: April 6th, 2025, 3:01 pm I also seem to get bugs on my touch device. On https://lazyslug.com/lifeviewer, after using the touch screen on it, LifeViewer no longer registers keyboard shortcuts.