I've noticed these on Chromium/Debian/X86, but they were mostly
manageable. However on the tf300t they make some operations impossible.
1. Selecting a unit and quickly hitting an action key works, but after
about 1ms the unit is unselected and the menu for the unit opens.
Selecting an option like Unit goto results in the error First select a
unit to move by clicking on it, then... Needless to say all the options
even tile info have no effect.
2. The simplest way to g is to drag the unit where you want to go.
Making sure not to run over any other unit, as doing so will select that
unit. Also using numbers has no effect, likely because there is no number
pad. This makes it impossible to move one unit to where another ?friendly?
unit is. This might effect attacking enemy units, not tested.
The testing was performed under cm-12.1 using Chrome with the optional
keyboard attached... I can't see freeciv web being playable without one.
The trackpad mouse works, but it doesn't do anymore then the touch screen
on the tablet.
I'm unsure if these are all the issues I've encountered, but they are the
most troubling. I may be enclined to wade through javascript looking for
the cause, if I had some idea of where to start... aside from greping for
the error and tracking backwards. As the menu no-longer has a pointer to
the unit I'd imagine a stack trace from that point leads you back to the
event dispatcher with nothing else of note.
___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev
