After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 170347 - User is stuck when using the repeat key on a drop-down menu
User is stuck when using the repeat key on a drop-down menu
Status: RESOLVED FIXED
Product: gok
Classification: Deprecated
Component: general
0.12.x
Other Linux
: Normal major
: ---
Assigned To: bill.haneman
bill.haneman
AP1
Depends on:
Blocks:
 
 
Reported: 2005-03-14 16:27 UTC by Gary Johnston
Modified: 2005-03-15 10:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Attachments
patch to fix, and make the combo popups work properly too (2.79 KB, patch)
2005-03-14 20:48 UTC, bill.haneman
accepted-commit_now Details | Review

Description Gary Johnston 2005-03-14 16:27:21 UTC
Using Linux Nightly build (from 14th march) and gok 0.12.4

Steps to reproduce:
* Start up GOK
* Click on UI Grab -> Launch -> Preferences -> Desktop Preferences -> Folders
* Click on Compose
* Click on Alt, z and then the spacebar
* Click on the repeat key (key below back)
* Click on down key

Note that the user will not be able to get on of this repeat down key because
everytime the a new value is choosen, the GOK screen refreshes the "back" choice
and the user can't disbale the repeat key!
Comment 1 bill.haneman 2005-03-14 16:36:37 UTC
I don't understand - the user can select the repeat key to turn it off, at any
time...
Comment 2 Gary Johnston 2005-03-14 16:50:27 UTC
To select the repeat key to turn it off, the user has to be able to go to GOK's
keyboard and unselect the repeat key.  However, everytime another option in the
drop-down menu is chosen (because it's repeatly going down the list), GOK
refreshes it's screen with the one and only option "Back".  So, what you have to
do is hit the mouse three times to choose back (scenario is in automatic
scanning - once to start scanning, once to choose row and once to choose column)
and then three times again when you're on the keyboard to unselect repeat. The
problem is you have less than one second to do this (because when a new option
is chosen you're back at the start again!) - Hope that helps!
Comment 3 David Bolter 2005-03-14 18:29:17 UTC
So there is a keyboard with only one key and that key is the back key?
Comment 4 bill.haneman 2005-03-14 18:40:18 UTC
I suspect the problem may be that the 'repeat' option isn't getting un-set when
the keyboard branches... not sure, as I have not reproduced.
Comment 5 bill.haneman 2005-03-14 18:47:19 UTC
Two issues: the repeat isn't getting properly cleared for some reason(this bug),
and also the combobox popup isn't producing a GOK menu=choices keyboard as one
would expect (probably gtk+ or gail bug).
Comment 6 David Bolter 2005-03-14 19:26:03 UTC
Gary, to cancel repeat mode the user is simply expected to perform an action
such as select a switch or button, or in the case of dwell, to leave a key
boundary. You shouldn't need to return to the repeat key itself to disarm it.  

But...

I do think you have discovered a flaw.  Bill and I are discussing.
Comment 7 David Bolter 2005-03-14 19:28:39 UTC
BTW, if you are brave you can explore the access method (*.xml.in) files in the
root gok source directory -- near the end of each is the logic for turning off
the repeat state.
Comment 8 David Bolter 2005-03-14 19:54:28 UTC
Aside: a workaround is to use UI Grab to access the items of the combo box.
However, this does not solve the problem of a user getting stranded.
Comment 9 bill.haneman 2005-03-14 20:48:41 UTC
Created attachment 38713 [details] [review]
patch to fix, and make the combo popups work properly too
Comment 10 David Bolter 2005-03-14 20:50:06 UTC
Comment on attachment 38713 [details] [review]
patch to fix, and make the combo popups work properly too

excellent. please commit.
Comment 11 Gary Johnston 2005-03-15 09:15:00 UTC
I realised what had to be done to stop the repeat but none of these options were
available because there was so little time to do them.
Comment 12 bill.haneman 2005-03-15 10:16:28 UTC
Gary: in comment #6, note that time is not an issue, since any key activation on
any button (in this case there is only one) should stop the key repeat.  David's
point is that any user activity involving a switch should stop the repeat,
there's no time limit on that as far as we can see.  There may be/have been a
bug impacting that, but any user switch action should stop the repeating.