GNOME Bugzilla – Bug 154566
GOK functionality is broken
Last modified: 2004-12-22 21:47:04 UTC
Some User Interface changes have been made to GOK which have caused functionality problems. -Activate the 'Bottom Panel' and select Launch. -The user is presented with 3 options : 'click', 'press', and 'release' -selecting any of these options does nothing. -the user is unable to activate any options on the Bottom Panel -'click', 'press', and 'release' options are not working, so the user cannot navigate beyond this point using GOK. Before these User Interface changes, once a user selected Launch, they were shown the list from the Launch Menu.
This was found in the Solaris nightly build from 4th Oct 2004. It is expected this bug will be present in Cinnabar Build_20.
Strange. Sound like a regression that might be caused by the fix for bug 151417. But in that case I would expect the actions to work... are you using the core pointer to operate GOK in this situation. Either way, I think showing the actions in this case is unecessary.
No, I am using a 2nd mouse to activate GOK.
And the second mouse does not send core events right? Activating "click" does nothing? I think one potential fix here would be to remove the second and third actions from the Launch widget. I'm not sure this is ideal. We could try some heuristic in GOK to ignore what GOK perceives as redundant actions... this would avoid GOK building an actions keyboard in this case.
Frances are you able to apply Bill's patch: http://bugzilla.gnome.org/attachment.cgi?id=32248&action=view (from bug 154570) I'd like to confirm that this allows you to select the click action.
*** This bug has been marked as a duplicate of 154570 ***
The 'UI changes' are perhaps better described as behavioral changes, as the basic visual UI is the same.
*** Bug 154826 has been marked as a duplicate of this bug. ***
Just a note on this closed bug to say that bug 154604 has a patch which might also be helpful here.
Bill, Frances needs a nightly build or a package including your fix for 154570 to test.
this is fixed in the recent nightly build, and in cvs.
BTW it's fixed in the respin too.