On Thu, May 7, 2009 at 5:09 AM, Li Yuan <li.y...@sun.com> wrote: >> >> Ok, I can explore that idea. Filed as >> http://bugzilla.gnome.org/show_bug.cgi?id=581605 >> for now. >> > > I think this is a good idea.
I had a look at it. Unfortunately, the entry icon api doesn't really make this possible. We only have icon-press/icon-release signals, and the menus, etc are all handled application-side. The only thing I could come up with so far is a activate-icon keybinding signal, that can be bound to various key combinations to simulate icon-press and release events on the icons. This is really not very nice. The patch I have attached to the bug does Ctrl-Enter -> send icon-press/icon-release for button 1 on the primary icon Ctrl-Shift-Enter-> send the same for button 1 on the secondary icon Ctrl-Menu -> send icon-press/icon-release for button 3 on the primary icon Ctrl-Shift-Menu -> send icon-press/icon-release for button 3 on the secondary icon The application code then needs to be careful to make the menu behave well as a keyboard-triggered menu when the send_event flag in the event is set. Ugly, ugly. Matthias _______________________________________________ Gnome-accessibility-devel mailing list Gnome-accessibility-devel@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
