Page 13 of 20

Re: Lifeviewer Bugs

Posted: December 27th, 2023, 12:16 pm
by azulavoir
rowett wrote:
December 26th, 2023, 3:20 pm
Please let me know which version of Android you are running. There haven't been any significant changes to LifeViewer recently.
This issue occurs in Chrome 120.0.6099.144 on Android 14.

Re: Oscillator with no rotor?

Posted: January 5th, 2024, 4:36 pm
by rowett
b-engine wrote:
December 25th, 2023, 7:09 am
LifeViewer identifies that 1-cell on-off has both active rotor cells, volatility, temperature and heat of 0 (which is impossible for any oscillator) even through it's period and mod is 2.

Code: Select all

x = 1, y = 1, rule = B3/S23Investigator
J!
Fixed, thanks. LifeViewer treats the off version of on-off [R]Investigator pairs as a dead cell during Identify.

Re: Oscillator with no rotor?

Posted: January 6th, 2024, 1:22 am
by Haycat2009
rowett wrote:
January 5th, 2024, 4:36 pm
b-engine wrote:
December 25th, 2023, 7:09 am
LifeViewer identifies that 1-cell on-off has both active rotor cells, volatility, temperature and heat of 0 (which is impossible for any oscillator) even through it's period and mod is 2.

Code: Select all

x = 1, y = 1, rule = B3/S23Investigator
J!
Fixed, thanks. LifeViewer treats the off version of on-off [R]Investigator pairs as a dead cell during Identify.
Another bug: Strict voltility and voltility should be 1, as there is 1 cell that oscillates at that period. Heat should be 1, and temp should be 1.

Re: Oscillator with no rotor?

Posted: January 6th, 2024, 3:19 am
by rowett
Haycat2009 wrote:
January 6th, 2024, 1:22 am
Another bug: Strict voltility and voltility should be 1, as there is 1 cell that oscillates at that period. Heat should be 1, and temp should be 1.
They are. You need to hard refresh your browser to ensure you have the latest build (1098).

Re: lifeviewer bugs

Posted: January 17th, 2024, 1:38 am
by b-engine
Press Ctrl+A+Space and you'll see the bug:

Code: Select all

x = 5, y = 4, rule = R3,C2,S5-9,B7-9,N#
b3o$2b2o$5o$b2obo!
EDIT:
Lifeviewer identifies that the oscillator has minpop of 14, but it's minpop is actually 13.

Code: Select all

x = 6, y = 7, rule = Symbiosis
2.A$3.A$.A2.AB$.2A.A$A2.B$.2A$.B!

Re: lifeviewer bugs

Posted: January 17th, 2024, 11:10 am
by rowett
b-engine wrote:
January 17th, 2024, 1:38 am
Press Ctrl+A+Space and you'll see the bug:
I don't see a bug. Ctrl+Space means advance selection after which use Enter to paste or Esc to remove.
b-engine wrote:
January 17th, 2024, 1:38 am
Lifeviewer identifies that the oscillator has minpop of 14, but it's minpop is actually 13.
On my system it shows min population as 13:
minpop.png
minpop.png (18.83 KiB) Viewed 30951 times

Re: lifeviewer bugs

Posted: January 18th, 2024, 1:13 am
by b-engine
rowett wrote:
January 17th, 2024, 11:10 am
b-engine wrote:
January 17th, 2024, 1:38 am
Press Ctrl+A+Space and you'll see the bug:
I don't see a bug. Ctrl+Space means advance selection after which use Enter to paste or Esc to remove.
This is what I see after pressing Ctrl+A+Space:

Re: lifeviewer bugs

Posted: January 18th, 2024, 3:20 am
by rowett
b-engine wrote:
January 18th, 2024, 1:13 am
This is what I see after pressing Ctrl+A+Space:
Yes that's expected. When you do Ctrl+Space it advances cells in the selection only which is shown as an overlay.

Re: lifeviewer bug

Posted: January 23rd, 2024, 11:24 pm
by Haycat2009
Bug:

1. Copy this text

2. Use the Copy all clipboard function on mobile

3. You do not get the rle, but this text.

Re: lifeviewer bug

Posted: January 24th, 2024, 8:00 am
by rowett
Haycat2009 wrote:
January 23rd, 2024, 11:24 pm
Bug:

1. Copy this text

2. Use the Copy all clipboard function on mobile

3. You do not get the rle, but this text.
If you're using Safari then this bug may have been fixed in build 1100.

Re: lifeviewer bug

Posted: January 24th, 2024, 4:43 pm
by AlbertArmStain
Here's something like a bug:
if you move your mouse up, the "y" position in the bottom left hand corner goes down (at least on lazyslug.com)

Re: lifeviewer bug

Posted: January 24th, 2024, 5:29 pm
by rowett
AlbertArmStain wrote:
January 24th, 2024, 4:43 pm
Here's something like a bug:
if you move your mouse up, the "y" position in the bottom left hand corner goes down (at least on lazyslug.com)
It's meant to.

Re: lifeviewer bug

Posted: January 24th, 2024, 9:09 pm
by Haycat2009
rowett wrote:
January 24th, 2024, 8:00 am
Haycat2009 wrote:
January 23rd, 2024, 11:24 pm
Bug:

1. Copy this text

2. Use the Copy all clipboard function on mobile

3. You do not get the rle, but this text.
If you're using Safari then this bug may have been fixed in build 1100.
Even on Safari it does not work.

Re: Lifeviewer Bugs

Posted: January 31st, 2024, 11:25 am
by azulavoir
rowett wrote:
December 26th, 2023, 3:20 pm
azulavoir wrote:
December 25th, 2023, 10:25 pm
https://youtu.be/ANu9crNiq2M

I don't know if it's the most recent android or what but Lifeviewer is extremely flickery and barely functional on mobile for me.
Anyone else on Android experiencing this issue?
I'd love to know if it's just me and my Pixel 6a having this... it's definitely intrusive to Lifeviewing and it's still happening for me.

Re: lifeviewer bug

Posted: January 31st, 2024, 12:17 pm
by snowman
Galaxy S10 here, LifeViewer works fine for me.

Re: lifeviewer bug

Posted: February 1st, 2024, 6:12 am
by rowett
Haycat2009 wrote:
January 24th, 2024, 9:09 pm
Even on Safari it does not work.
I can't reproduce this. I've tested on both iOS and Android and it works for me. Anyone else seeing this issue?

Re: lifeviewer bugs

Posted: February 2nd, 2024, 3:19 am
by b-engine
rowett wrote:
January 17th, 2024, 11:10 am
On my system it shows min population as 13:

-
This bug appears again. The infobox displays that the minpop is 30, but the identifier says that the minpop is 29.

Re: lifeviewer bugs

Posted: February 2nd, 2024, 4:08 am
by rowett
b-engine wrote:
February 2nd, 2024, 3:19 am
The infobox displays that the minpop is 30, but the identifier says that the minpop is 29.
The infobox is showing the current population (not the minimum).

Re: lifeviewer bugs

Posted: February 2nd, 2024, 4:11 am
by b-engine
rowett wrote:
February 2nd, 2024, 4:08 am
The infobox is showing the current population (not the minimum).
But you can see that the current population value on the graph is the lowest.

EDIT:
Finally found that problem: the graph is slightly off-phase - it displays the latest population few generations before instead of current generation.

Re: lifeviewer bugs

Posted: February 3rd, 2024, 12:34 pm
by rowett
b-engine wrote:
February 2nd, 2024, 4:11 am
the graph is slightly off-phase - it displays the latest population few generations before instead of current generation.
This is only true when the number of generations T is greater than the horizontal resolution of the graph.

Re: lifeviewer bug

Posted: February 7th, 2024, 5:58 pm
by azulavoir
I'm not sure if this is a bug or what it is, but.... Whatever's going on here.

Both of these, which you'd think would be alternating rules between the two tables, are instead Symbiosis with the colors of HighAndLow. The order of the ruletables doesn't matter, and the order of the rules doesn't matter either. And if you leave the tables out, this just doesn't let you load the viewer.

Code: Select all

x = 0, y = 0, rule = Symbiosis|HighAndLowLife
!

@RULE Symbiosis

https://conwaylife.com/forums/viewtopic.php?p=21425#p46301

@TREE

num_states=3
num_neighbors=8
num_nodes=64
1 0 0 0
1 0 0 2
1 0 1 0
2 0 1 2
1 0 1 2
2 1 4 4
2 2 4 4
3 3 5 6
1 1 1 2
2 4 8 4
2 4 4 4
3 5 9 10
1 2 1 2
2 4 4 12
3 6 10 13
4 7 11 14
2 8 1 4
3 9 16 10
3 10 10 10
4 11 17 18
2 12 4 2
3 13 10 20
4 14 18 21
5 15 19 22
2 1 1 4
3 16 24 10
4 17 25 18
4 18 18 18
5 19 26 27
2 2 4 2
3 20 10 29
4 21 18 30
5 22 27 31
6 23 28 32
3 24 24 10
4 25 34 18
5 26 35 27
5 27 27 27
6 28 36 37
3 29 10 29
4 30 18 39
5 31 27 40
6 32 37 41
7 33 38 42
4 34 34 18
5 35 44 27
6 36 45 37
6 37 37 37
7 38 46 47
4 39 18 39
5 40 27 49
6 41 37 50
7 42 47 51
8 43 48 52
5 44 44 27
6 45 54 37
7 46 55 47
7 47 47 47
8 48 56 57
5 49 27 49
6 50 37 59
7 51 47 60
8 52 57 61
9 53 58 62

@TABLE

n_states:3
neighborhood:Moore
symmetries:permute
1,0,0,0,0,0,0,0,0,0
1,1,0,0,0,0,0,0,0,0
0,1,1,1,0,0,0,0,0,1
1,1,1,1,1,0,0,0,0,0
1,1,1,1,1,1,0,0,0,0
1,1,1,1,1,1,1,0,0,0
1,1,1,1,1,1,1,1,0,0
1,1,1,1,1,1,1,1,1,0
2,0,0,0,0,0,0,0,0,0
2,2,0,0,0,0,0,0,0,0
0,2,2,2,0,0,0,0,0,2
2,2,2,2,2,0,0,0,0,0
2,2,2,2,2,2,0,0,0,0
2,2,2,2,2,2,2,0,0,0
2,2,2,2,2,2,2,2,0,0
2,2,2,2,2,2,2,2,2,0

@RULE HighAndLowLife

https://conwaylife.com/forums/viewtopic.php?f=11&t=6196
https://conwaylife.com/forums/viewtopic.php?p=169699#p169699

@COLORS
0 0 0 0
1 0 128 128
2 0 255 255

@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a1 = {0, 1, 2}
var a2 = {0, 1, 2}
var a3 = {0, 1, 2}
var a4 = {0, 1, 2}
var a5 = {0, 1, 2}
var a6 = {0, 1, 2}
var a7 = {0, 1, 2}
var a8 = {0, 1, 2}
var b = {0, 1}
var c = {0, 2}
var d = {1, 2}

1, 1, 1, 0, 0, 0, 0, 0, 0, 1
1, 2, 0, 0, 0, 0, 0, 0, 0, 1

b, 1, 1, 1, 0, 0, 0, 0, 0, 1
b, 1, 2, 0, 0, 0, 0, 0, 0, 1

2, 1, 1, 1, 1, 0, 0, 0, 0, 2
2, 1, 1, 2, 0, 0, 0, 0, 0, 2
2, 2, 2, 0, 0, 0, 0, 0, 0, 2

2, 1, 1, 1, 1, 1, 0, 0, 0, 2
2, 1, 1, 1, 2, 0, 0, 0, 0, 2
2, 2, 2, 1, 0, 0, 0, 0, 0, 2

c, 1, 1, 1, 1, 1, 1, 0, 0, 2
c, 1, 1, 1, 1, 2, 0, 0, 0, 2
c, 1, 1, 2, 2, 0, 0, 0, 0, 2
c, 2, 2, 2, 0, 0, 0, 0, 0, 2

2, 1, 1, 1, 1, 1, 1, 1, 0, 2
2, 1, 1, 1, 1, 1, 2, 0, 0, 2
2, 1, 1, 1, 2, 2, 0, 0, 0, 2
2, 1, 2, 2, 2, 0, 0, 0, 0, 2

d, a1, a2, a3, a4, a5, a6, a7, a8, 0

Code: Select all

x = 0, y = 0, rule = HighAndLowLife|Symbiosis
!

@RULE HighAndLowLife

https://conwaylife.com/forums/viewtopic.php?f=11&t=6196
https://conwaylife.com/forums/viewtopic.php?p=169699#p169699

@COLORS
0 0 0 0
1 0 128 128
2 0 255 255

@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a1 = {0, 1, 2}
var a2 = {0, 1, 2}
var a3 = {0, 1, 2}
var a4 = {0, 1, 2}
var a5 = {0, 1, 2}
var a6 = {0, 1, 2}
var a7 = {0, 1, 2}
var a8 = {0, 1, 2}
var b = {0, 1}
var c = {0, 2}
var d = {1, 2}

1, 1, 1, 0, 0, 0, 0, 0, 0, 1
1, 2, 0, 0, 0, 0, 0, 0, 0, 1

b, 1, 1, 1, 0, 0, 0, 0, 0, 1
b, 1, 2, 0, 0, 0, 0, 0, 0, 1

2, 1, 1, 1, 1, 0, 0, 0, 0, 2
2, 1, 1, 2, 0, 0, 0, 0, 0, 2
2, 2, 2, 0, 0, 0, 0, 0, 0, 2

2, 1, 1, 1, 1, 1, 0, 0, 0, 2
2, 1, 1, 1, 2, 0, 0, 0, 0, 2
2, 2, 2, 1, 0, 0, 0, 0, 0, 2

c, 1, 1, 1, 1, 1, 1, 0, 0, 2
c, 1, 1, 1, 1, 2, 0, 0, 0, 2
c, 1, 1, 2, 2, 0, 0, 0, 0, 2
c, 2, 2, 2, 0, 0, 0, 0, 0, 2

2, 1, 1, 1, 1, 1, 1, 1, 0, 2
2, 1, 1, 1, 1, 1, 2, 0, 0, 2
2, 1, 1, 1, 2, 2, 0, 0, 0, 2
2, 1, 2, 2, 2, 0, 0, 0, 0, 2

d, a1, a2, a3, a4, a5, a6, a7, a8, 0


@RULE Symbiosis

https://conwaylife.com/forums/viewtopic.php?p=21425#p46301

@TREE

num_states=3
num_neighbors=8
num_nodes=64
1 0 0 0
1 0 0 2
1 0 1 0
2 0 1 2
1 0 1 2
2 1 4 4
2 2 4 4
3 3 5 6
1 1 1 2
2 4 8 4
2 4 4 4
3 5 9 10
1 2 1 2
2 4 4 12
3 6 10 13
4 7 11 14
2 8 1 4
3 9 16 10
3 10 10 10
4 11 17 18
2 12 4 2
3 13 10 20
4 14 18 21
5 15 19 22
2 1 1 4
3 16 24 10
4 17 25 18
4 18 18 18
5 19 26 27
2 2 4 2
3 20 10 29
4 21 18 30
5 22 27 31
6 23 28 32
3 24 24 10
4 25 34 18
5 26 35 27
5 27 27 27
6 28 36 37
3 29 10 29
4 30 18 39
5 31 27 40
6 32 37 41
7 33 38 42
4 34 34 18
5 35 44 27
6 36 45 37
6 37 37 37
7 38 46 47
4 39 18 39
5 40 27 49
6 41 37 50
7 42 47 51
8 43 48 52
5 44 44 27
6 45 54 37
7 46 55 47
7 47 47 47
8 48 56 57
5 49 27 49
6 50 37 59
7 51 47 60
8 52 57 61
9 53 58 62

@TABLE

n_states:3
neighborhood:Moore
symmetries:permute
1,0,0,0,0,0,0,0,0,0
1,1,0,0,0,0,0,0,0,0
0,1,1,1,0,0,0,0,0,1
1,1,1,1,1,0,0,0,0,0
1,1,1,1,1,1,0,0,0,0
1,1,1,1,1,1,1,0,0,0
1,1,1,1,1,1,1,1,0,0
1,1,1,1,1,1,1,1,1,0
2,0,0,0,0,0,0,0,0,0
2,2,0,0,0,0,0,0,0,0
0,2,2,2,0,0,0,0,0,2
2,2,2,2,2,0,0,0,0,0
2,2,2,2,2,2,0,0,0,0
2,2,2,2,2,2,2,0,0,0
2,2,2,2,2,2,2,2,0,0
2,2,2,2,2,2,2,2,2,0

Re: lifeviewer bug

Posted: February 7th, 2024, 7:10 pm
by rowett
azulavoir wrote:
February 7th, 2024, 5:58 pm
I'm not sure if this is a bug or what it is, but.... Whatever's going on here.
LifeViewer does not support alternating rules where either of the rules is a RuleLoader (@TABLE or @TREE) rule.
It should flag this as an error.

EDIT: LifeViewer now reports these as not supported.

Re: lifeviewer bug

Posted: February 10th, 2024, 6:20 pm
by confocaloid

Code: Select all

x = 74, y = 74, rule = B3/S23
37bo$37b3o$40bo$39b2o13b2o$54bo$52bobo$52b2o2$43bo$42bobo$42bobo$42b2o3$31bo$
30bo8b2o$17bo12b3o7bo$17b3o17b3o17b2o$20bo16bo19bo$3bo15b2o34bobo$3b3o42bo6b
2o$6bo39b2ob2o$5b2o39b2ob2o$46b2o2bo$23bo17b2o5b2o$21b2obo6b2o7bobo$21bo2bo6b
2o7bo$21b3o15b2o3$8bobo46b3o$7bo2bo37b2o7bo$9b2o13b2o22b2o8bo$24bo$2b2o11b2o
8b3o$bobo11bobo9bo$bo15bo37b2o15b2o$2o15b2o37bo15bo$46bo9bobo11bobo$46b3o8b2o
11b2o$49bo$15bo8b2o22b2o13b2o$16bo7b2o37bo2bo$14b3o46bobo3$33b2o15b3o$33bo7b
2o6bo2bo$31bobo7b2o6bob2o$24b2o5b2o17bo$23bo2b2o$23b2ob2o39b2o$23b2ob2o39bo$
17b2o6bo42b3o$16bobo34b2o15bo$16bo19bo16bo$15b2o17b3o17b3o$33bo7b3o12bo$33b2o
8bo$42bo3$30b2o$29bobo$29bobo$30bo2$20b2o$19bobo$19bo$18b2o13b2o$33bo$34b3o$
36bo!
Identifying this oscillator (Pattern/Identify) shows that the minimum population is 246 and the maximum population is 476. After that, the section "Identify" in Help/Info says: "T Min/Max 246@T3 476@T14". However, generation 3 of the above pattern has population 270 (instead of expected 246), and generation 14 has population 436 (instead of expected 476).

Re: lifeviewer bug

Posted: February 10th, 2024, 6:45 pm
by rowett
confocaloid wrote:
February 10th, 2024, 6:20 pm
Identifying this oscillator (Pattern/Identify) shows that the minimum population is 246 and the maximum population is 476. After that, the section "Identify" in Help/Info says: "T Min/Max 246@T3 476@T14". However, generation 3 of the above pattern has population 270 (instead of expected 246), and generation 14 has population 436 (instead of expected 476).
It's because the T Min/Max values are an offset from the generation that the oscillator was detected. If you look a few lines further down in Help>Info>Identify you'll see "Generation 37 and 78". This means the oscillator was detected from generations 37 to 78 (hence period 41). The T Min value is 3 generations from the beginning (i.e. 37 + 3 = 40) and the T Max value is 14 generations from the beginning (i.e. 37 + 14 = 51).

Re: lifeviewer bug

Posted: February 19th, 2024, 6:19 pm
by rokicki
LifeViewer does not appear to stop propagation of keyboard events (even ones it processes) which leads to issues when you embed a LifeViewer in another context (such as a reveal.js presentation).

Code: Select all

<!DOCTYPE html>
<html>
<head>
<meta name="LifeViewer" content="viewer textarea"> <!--required tag-->
<script src="lv-plugin.js"></script> <!--assumes plug-in is in the same directory as html file-->
<script>
function showkey(e) {
   document.getElementById("disp").textContent += " " + e.code ;
}
window.onload = function() {
   document.getElementById("bubblediv").addEventListener("keydown", showkey);
}
</script>
</head>
<body>
<!--viewer container-->
<div id="bubblediv">
<div class="viewer"> <!--class=viewer is required-->
	<textarea>bo$2bo$3o!</textarea><br/> <!--textarea required in viewer container, with glider rle-->
	<canvas></canvas> <!--canvas required in viewer container-->
</div>
</div>
<!--end viewer container-->
<div id="disp"></div>
</body>
</html>
My workaround for now is to embed each LifeViewer in another div that swallows keyboard events, but that's
just masking the bug and can lead to other issues.