[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gtk-app-devel
Subject:    how to hint gtk about a useful start of the focus chain
From:       Stefan Kost <ensonic () hora-obscura ! de>
Date:       2011-08-02 10:10:27
Message-ID: 4E37CD13.2050507 () hora-obscura ! de
[Download RAW message or body]

hi,

having the focus on the right widget can make apps more productive. I feed that right \
now either I am missing something or gtk does not a good job at it.

For odd reasons gtk prefers to focus toolbar button on new windows (which is
strange and not useful imho). When trying to hint gtk+ about what a useful focus
behavior I came across gtk_button_get_focus_on_click(). The documentations
says "Making mouse clicks not grab focus is useful in places like toolbars
where you don't want the keyboard focus removed from the main area of the
application.". Although this function cannot be used with toolbar buttons as those \
are toolitems. Then I discovered that gtktoolitem.c seems to actually call this \
internaly. http://git.gnome.org/browse/gtk+/tree/gtk/gtktoolbutton.c?h=gtk-2-24#n308

Should the docs be changed to mention that for toolbars its helpful for
toolitem implementations?

Should gtk take that flag into account when determining the widget that gets
focus in a new window. Right now it stubbornly focuses on the toolitem. No
matter how hard I try (e.g. gtk_widget_grab_focus(other_widget) in window::show
signal handler).

Any tips? What are you guy using to set a proper focus on new windows/dialogs.

Stefan


_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


[prev in list] [next in list] [prev in thread] [next in thread]