GNOME Bugzilla – Bug 157358
gok user option is needed for action reducing heuristics
Last modified: 2011-10-14 11:00:40 UTC
At the time of this bug (RFE), gok currently circumvents the display of a typical button actions keyboard (click, press, release) and simply performs a "click" action. Other similar time-saving techniques might be created in the future. A suggestion was made by Harry (in bug 154604) to include a user option so that all the actions can be exposed to the user.
Copy comments from Bug 154604 and 155556 ------- Additional Comment #11 From Harry Lu 2004-11-03 22:27 ------- I have some concerns here. As I can see from some codes, not everyone connect to the "clicked" signal of a gtkbutton. Some just connect to the "pressed" signal, and in some cases, they connect to "button_press_event" signal. So their signal handling function won't be called when you just let the button emit a "clicked" signal. In gailbutton.c, the action "press" will simulate a button press event. So their function can be called when doing the action "press". So I think leave the 3 actions there, user can try "click" first, if this doesn't work, he might then try "press". Or maybe GOK could have a option to let user choose whether showing all actions. ------- Additional Comment #12 From David Bolter 2004-11-04 09:06 ------- I think having a user option is a good idea. Ideally the first exposed action (at the first index) would be the primary action for a given component but it sounds like that would require extra effort from the application developer. I don't like relying on this. Bill, your thoughts? ------- Additional Comments From bill.haneman@sun.com 2004-11-04 09:45 ------- I think exposing only "click" is OK if click is the first of 3 actions. For the cases we know about, "press" is the first action for things that connect to the button-press/release signals. The alternative, always showing all 3 actions, causes a problem because it requires a whole new choice from the GOK user, and for switch users this can represent a serious efficiency loss.
Bill, I know in some cases (arrow button whose parent is "ColorCombo"), the "press" is the first action for gtkbutton. This is too hacky I think. And in some others cases of Evolution (and I believe in some other applications), they also need "press" as the default action.
If anything other than 'click' is the first (default) action, then we expose all the actions now. I think this is sufficient, personally. An option to expose all actions would be a lower-priority RFE, and not on by default IMO.
Bill, there is an internal bugster bug #6198461 depending on this bug.
Harry, I think the better solution is to make 'press' the default action for GUI components which use 'press' and not 'click'. The action reducing heuristics in GOK made an enormous difference in user effectiveness, and removing them (or even turning them off!) because of one app like evolution is not good for the user either.
To build consensus here, I agree with Bill on this point: The primary action should be the first indexed action.
As I checked, in Evolution Trunk's code, it connected to "clicked" signal of the button. So this won't be a problem for Evolution Trunk.
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
gok (GNOME on-screen keyboard) development has been stalled and it has been replaced by caribou [1]. Maintainers don't have future development plan so i am closing all the bugs as WONTFIX. [1] https://mail.gnome.org/archives/gnome-bugsquad/2011-October/msg00001.html