> GTK has extensive internal support for "key navigation" that allows > users to move keyboard focus and > which-widget-will-be-activated-by-default around a GUI without having > to resort to the mouse. > > The keys above are all involved in this support, although Return plays > a special role - it activates the current default widget, if any. This > means that GTK prevents them from being used as accelerators. I know. In first place I tried to remove standart bindings, but trap was in other place. > For a few apps (like the one I work on) its generally a liability. Just now I working on the application without any widgets in main window which need such navigation. >There are ways around it but they are complex and a bit ugly. If it can save whole functionality of standart accels (like shortcut labels in menu or accel maps) I am ready to anything. Give me a hint please. > I am currently thinking about a patch that makes the use of these keys > for key-nav optional at the request of the application and/or user. > Not likely to surface any time soon, though. This will be excellent, I think. _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
