https://bugzilla.novell.com/show_bug.cgi?id=382755
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=382755#c8
--- Comment #8 from Stefan Hundhammer
We redraw the Welcome screen (usibg the currently selected language) with every single "&Language" change because we want users to read the license in their language and we want user to select "I Agree to the License Terms" there.
I know all that. That (and the resulting slowness) was the reason why we used to have the language selection in a separate dialog. Plus, of course, not overwhelming the user with a lot of text in a language he might not understand, and in a pretty complex dialog where he might not figure out that there is a language at all, and if so, where it might be. This is IMHO much worse from a usability point of view.
In ncurses, [arrow down] opens a list of available languages and users can scroll through the list to select a new language.
The NCurses UI is not the Qt UI. They have always been and will always be different. That's the point of having multiple UIs. Strictly speaking, it's a bug that an NCComboBox doesn't deliver an event when the user makes a change, not that the YQComboBox does. That's the point of `opt(`notify) flag. The NCComboBox (and also the NCSelectionBox) are pardoned about that only because there is no other way for the user to select anything without selecting other (undesired) items in the process; that causes slowness in all kinds of other scenarios, too. Graphical UIs (Qt, Gtk) have a mouse, and that's the common way to select items in those widgets; there is no general need to temporarily select items you don't realls want to select. That's all extensively documented in the events documentation, BTW. This scenario is unique in the way that a mouseless installation can happen (though pretty rarely these days), and the show must still go on. In that scenario (and in that one alone) it is really annoying to be unable to use the preferred method (using the mouse) of selecting combo box or selection box items and having to select intermediate items with the keyboard instead. As I wrote in comment #3 .. comment #5, we _could_ add `opt(`immediate) to the combo box widget, thus changing the default behaviour of `opt(`notify) combo boxes. But I really don't know in how many other places that might create problems. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.