From: Marc M. <Marc.Mulcahy@Sun.COM> - 2004-03-08 08:09:04
|
Hi Nathan, Gaim as it exists in CVS is difficult to use, sine although the gtkimhtml widget is accessible via the keyboard, is isn't focussable. Ths appears to be for two reasons-- one is that shift-tabs get passed to the gtkimhtml and then cause the focus to shift back to the entry. This diff fixes this by adding GDK_ISO_Left_Tab to the list of allowed keys in the gtkimhtml. The other issue is, as we've discussed previously, related to the fact that the conversation container has a signal handler on it for "focus" which always puts the focus in the entry. This makes it impossible, using only the keyboard, to focus anything but the entry. You had mentioned previously that removing the signal handler for "focus" had some undesirable side-effect in chat windows. I think it related to switching tabs. When I switch tabs to a different chat, the focus seems to be placed in the correct widget for me. Could you give me some pointers about what the desired behavior is. I'd like to implement some code to get this issue fixed, since Gaim is difficult to use as it stands now. This diff removes the focus signal handler on the pane, and adds the GDK_ISO_Left_Tab key to the allowable keys for gtkimhtml widgets. I'm successfully using Gaim with this patch and Gnopernicus now. Marc On Fri, 30 Jan 2004, Nathan Fredrickson wrote: > Hi Marc, > > On Wed, 2004-01-28 at 19:04, Marc Mulcahy wrote: > > 1. The "focus" signal handler on the pane which forces focus to the > > outgoing entry doesn't allow one to tab and shift tab off the outgoing > > text entry, removing it makes things work great for me. > > I'm the one responsible for re-adding that signal handler which your > original patch removed. It was re-added to fix a focusing issue in chat > windows (only chat, not IM windows). > > When switching tabs in a chat window, focus is supposed to go to the > message entry box, but instead it's going to the topic entry box. It > appears that the panel gets focused first which in turn focuses the > first focusable widget: the topic entry. > > I'm sure there is a better method to focus the message entry first, and > then the signal handler on the pane can be removed. Patches welcome :-) > > > 2. It might be nice to also include home and end as keys which are allowed > > to be typed into the gtkimhtml. > > I agree, especially since we're already including the arrow keys. I'll > make a patch as soon as I can connect to the anoncvs to update my tree. > > > Thanks so much for doing all this work! I love using Gaim! > > Thanks for all the accessibility work you've done on Gaim. > > Nathan > > > |