There's a good chance that you can't use the pan function on mobile (maybe also happens in other touchscreen devices). When you tap somewhere in the viewer window, it seems to be like holding the "cursor".
This seems to be like holding mouse over a button
Screenshot_2024-04-04-14-16-06-42_40deb401b9ffe8e1df2f1cc5ba480b12.jpg (73.99 KiB) Viewed 9414 times
This had frustrated me for a long time, while the bug seems to haven't been noticed by someone else yet.
b-engine wrote: April 4th, 2024, 2:19 am
There's a good chance that you can't use the pan function on mobile (maybe also happens in other touchscreen devices). When you tap somewhere in the viewer window, it seems to be like holding the "cursor".
I can't reproduce this.
What device are you using?
Which browser and version?
Anyone else seeing this issue?
Cyclotrons wrote: April 25th, 2024, 3:31 pm
Lifeviewer currently throws an error when trying to view the patterns in this post, despite previously being able to do so with no problem.
Here is the first snippet from the linked post, modified to replace the long rulestring with "example" both in the RLE header and in the appended @RULE header. It works. I believe the reason why there is an error in your post is because the specified rulename doesn't follow conventions for rulenames that are explained on the page https://golly.sourceforge.io/Help/formats.html#rulename
Fixing rulenames to follow conventions should fix the problem.
127:1 B3/S234cUser:Confocal/R (isotropic CA, incomplete)
Unlikely events happen.
My silence does not imply agreement, nor indifference. If I disagreed with something in the past, then please do not construe my silence as something that could change that.
Cyclotrons wrote: April 25th, 2024, 3:31 pm
Lifeviewer currently throws an error when trying to view the patterns in this post, despite previously being able to do so with no problem.
Bug: In an infinite-length cylinder, the middle section’s grey walls disappear when zooming out. I first found this bug in the titanic toroidal traveller page.
~ Haycat Durnak, a hard-working editor
Also, support Conway and Friends story mode!
I mean no harm to those who have tested me. But do not take this for granted.
Haycat2009 wrote: May 13th, 2024, 7:58 pm
Bug: In an infinite-length cylinder, the middle section’s grey walls disappear when zooming out. I first found this bug in the titanic toroidal traveller page.
They don't disappear. The history trail is being displayed above them.
b-engine wrote: May 14th, 2024, 8:05 am
When I'm editing any wiki page the viewers are alway broken. Is there anyway to fix it?
Example from OCA:B2i3/S23, bug at top-right and bottom-left...
More specifics, please. If you click on the above wiki link and click the "Edit" tab, you won't see any failed attempts to render the page. Are you also clicking the "Preview" tab?
What OS are you running, and which browser? I don't see anything like the screenshot when I try "Preview" on Chrome in Windows 11.
dvgrn wrote: May 15th, 2024, 8:24 am
More specifics, please. If you click on the above wiki link and click the "Edit" tab, you won't see any failed attempts to render the page. Are you also clicking the "Preview" tab?
What OS are you running, and which browser? I don't see anything like the screenshot when I try "Preview" on Chrome in Windows 11.
I'm also in Windows 11, using Chrome version 124.0.6367.203. This bug always appears when I preview any page.
Seems that the bug also appears when I'm using another device to preview any page.
I was using lifeviewer and tried to copy a multi-state pattern when Google Chrome asked me if I wanted to allow "clipboard" for the forums. I clicked allow and tried to copy and paste the same pattern but when the copied pattern was placed, all non-zero states were set to state 1. I tried refreshing and tried copying and pasting a different multi-state pattern but that didn't work, so I disabled "allow clipboard" without refreshing and that seemed to fix the issue with the multi-state pattern.
AlbertArmStain wrote: May 16th, 2024, 5:24 pm
I was using lifeviewer and tried to copy a multi-state pattern when Google Chrome asked me if I wanted to allow "clipboard" for the forums. I clicked allow and tried to copy and paste the same pattern but when the copied pattern was placed, all non-zero states were set to state 1. I tried refreshing and tried copying and pasting a different multi-state pattern but that didn't work, so I disabled "allow clipboard" without refreshing and that seemed to fix the issue with the multi-state pattern.
LifeViewer will now attempt to use the external clipboard for Paste if the Sync button is enabled. Disable it to use the internal clipboard only.
LifeViewer respects the current rule when pasting from the system clipboard. So if a pattern with a 2-state rule is loaded and you paste a multi-state pattern any state > 0 will be pasted as state 1.
Run the pattern in this post after zooming out enough that the entire bounded grid is visible. When the spaceships hit the border they appear to eat away at the border, but when zooming in everything is normal.
EvinZL wrote: May 31st, 2024, 9:59 pm
Run the pattern in this post after zooming out enough that the entire bounded grid is visible. When the spaceships hit the border they appear to eat away at the border, but when zooming in everything is normal.
Platform: Edge on Windows 11
This is normal. The history trail is displayed over the border.
EvinZL wrote: May 31st, 2024, 9:59 pm
Run the pattern in this post after zooming out enough that the entire bounded grid is visible. When the spaceships hit the border they appear to eat away at the border, but when zooming in everything is normal.
Platform: Edge on Windows 11
That's intentional (live states and history states appear on top of the border), though I don't really feel like the history states specifically were meant to do so. Edit: Whoops, sniped.
x = 39, y = 10, rule = R4,C6,M1,S9..11,B8..9,NM
31.C$4.2D28.2D$C3.2D24.C3.2D$C2.3D11.E4.E7.C3.2D$C2A6D7.E6.E6.C2A6D$C
2AD.4D6.10E5.C2AD.4D$C2A3D10.E6.E6.3A4D$6A11.E4.E7.6A$AC4A3.C20.AC4A$
4A4C22.3A5C!
So this is a LifeViewer bug, not Catagolue/apgsearch.
(possibly because generations 2 and 5 have the same set of state 1 cells, then why is my pattern identified as p6?)
127:1 B3/S234cUser:Confocal/R (isotropic CA, incomplete)
Unlikely events happen.
My silence does not imply agreement, nor indifference. If I disagreed with something in the past, then please do not construe my silence as something that could change that.