GNOME Bugzilla – Bug 165748
return in New Image dialog should activate OK button
Last modified: 2008-01-15 12:46:51 UTC
Bring up a new image dialog. Hit return. Instead of creating a new image, the Template menu drops down. In previous versions of gimp, you could bring up the New Image dialog, hit return, and gimp would create a new image of the default size. Now, it takes 10 tabs to get to the Ok button; it's much harder to create a new image without using the mouse. Discussion on #gimp suggested that the change might be due to the change from GtkOptionMenu to GtkComboBox: option menus open on space, while combo boxes open on either return or space. So the combo box is eating the return that would otherwise go to the default button.
Just a small correction, it doesn't take 10 tabs. It takes pressing Shift-Tab once or, alternatively, pressing Tab four times. At this point the focus is not any longer in a widget that takes Enter and pressing Enter activates the dialog. After all, that's the default action of the New Image dialog.
Probably the best thing we can do here is to set the initial focus on the Image Width entry and set the "activates-default" flag on the width and height entries. That would be conformant with the HIG that suggests to put the initial focus on the widget that the user is most likely going to touch first. I guess for the most people that's either the Width entry or the OK button.
2005-02-09 Sven Neumann <sven@gimp.org> * libgimpwidgets/gimpsizeentry.[ch] * libgimpwidgets/gimpwidgets.def: added new function gimp_size_entry_set_activates_default(). * app/dialogs/image-new-dialog.c: set the initial focus on the Width entry and set the activates_default flag for the size entry. Fixes bug #165748.
*** Bug 303248 has been marked as a duplicate of this bug. ***
This is fixed for New Image, but the same problem applies to the New Layers dialog. Should I file a separate bug for that? I'll try to make a patch later, and check out some more dialogs to see what others might have similar problems.
Please not one more bug :-) This one is already a duplicate.
*** This bug has been marked as a duplicate of 148026 ***
*** Bug 430939 has been marked as a duplicate of this bug. ***