[Bug 443676] New: Inconsistent meaning of [OK] button in YaST
https://bugzilla.novell.com/show_bug.cgi?id=443676 Summary: Inconsistent meaning of [OK] button in YaST Product: openSUSE 11.1 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: mschmidkunz@novell.com ReportedBy: jsmeix@novell.com QAContact: qa@suse.de Found By: Development In the YaST style guide http://en.opensuse.org/YaST/Style_Guide#Single_Configuration.2FOverview.2FEd... it is not clear what the [OK] button in a Single Configuration/Overview/Edit Dialog should do because it only reads: "OK - The settings are applied and the screen is closed." It is not clear what "the screen is closed" means. Should it close the dialog and return to the overview or should it close the dialog and exit the whole YaST module? The current YaST printer module, behaves inconsistently because of this. If there is a single step configuration dialog as a branch of another configuration dialog (i.e. the "Add Driver" and "Driver Options" dialogs which are called e.g. from the "Modify print queue" dialog) the [OK] button in a single step configuration branch dialog returns to the caller (e.g. the "Modify print queue" dialog). In conrast if there is a single step configuration dialog on the top level of the tree of dialogs (e.g. the "Printing via Network" and "Share Printers" dialogs) the [OK] button in a top-level single step configuration dialog exits the whole YaST printer module. The problem here is that for the user it is not obvious if the current configuration dialog is at a lower-level ([OK] returns to the caller) or at top-level ([OK] exits the whole YaST printer module). At least for me (am I the only one?) it happens often that I click [OK] and get the whole module closed but I liked to do some other settings in other top-level dialogs so that I have to re-launch the module again. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=443676
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=443676#c1
--- Comment #1 from Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=443676
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=443676#c2
--- Comment #2 from Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=443676
User mschmidkunz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=443676#c3
--- Comment #3 from Martin Schmidkunz
https://bugzilla.novell.com/show_bug.cgi?id=443676
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=443676#c4
--- Comment #4 from Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=443676
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=443676#c5
--- Comment #5 from Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=443676
User mschmidkunz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=443676#c6
--- Comment #6 from Martin Schmidkunz
https://bugzilla.novell.com/show_bug.cgi?id=443676
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=443676#c7
--- Comment #7 from Johannes Meixner
participants (1)
-
bugzilla_noreply@novell.com