sam chording failures where acme and rio work fine

[GoogleCodeExporter]

in 9vx, i have chorded in acme and rio for years with no strange behaviour, no 
failures.

with the same hardware and the same 9vx binary, chording in sam fails. today i 
particularly observe the button-3 menu appearing in a 1-3 chord *while* button 
1 is still held down. this is easy to observe if the last item selected in the 
button-3 menu is "~~sam~~" which selects the command window. it's random, about 
50:50 whether the menu comes up or the chord succeeds, despite the fact that i 
do not release button 1 at this stage.

i expect the only part 9vx has to play in all this is simply being slower than 
real hardware.

Original issue reported on code.google.com by tereniao...@gmail.com on 1 Jun 2014 at 7:53

[GoogleCodeExporter]

Do you run 9front on 9vx?

Original comment by iru.mu...@gmail.com on 9 Jan 2015 at 5:51

[GoogleCodeExporter]

I did, for about three years altogether. For two of those years I ran the 9vx 
instance as a regular terminal, mounting its fs from my native fileserver. 
Problems were rare, but I didn't expect too much. I've now switched to 
accessing my Plan 9 session over VNC, it suits my lifestyle better.

----

I just checked; the problem still occurs when running sam under vncs with 
vncviewer from tightvnc as the client under linux/xorg. It does not occur when 
the client is vncv under native 9front. I also have problems with scrolling 
acme using the tightvnc client, as well as with p9p acme under the same xorg 
instance, so I'm inclined to write this off as a general xorg problem.

Original comment by tereniao...@gmail.com on 21 Jan 2015 at 3:49

• Added labels: Priority-Low
• Removed labels: Priority-Medium