[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 <jsmeix@novell.com> 2008-11-11 03:36:35 MST --- Created an attachment (id=251282) --> (https://bugzilla.novell.com/attachment.cgi?id=251282) A mail which also describes what I mean. -- 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#c2 --- Comment #2 from Johannes Meixner <jsmeix@novell.com> 2008-11-12 07:16:00 MST --- No response but I have no time to wait until a final solution is found. Meanwhile I seem to know how to manually control it so that I can now implement whatever the meaning of the [OK] button in a particular dialog should be. To avoid incosistencies I implemented now a consistent meaning of the [OK] button in yast2-printer version 2.17.36 which is "return to the caller" everywhere except for the Overview dialog where the [OK] button exits the whole module. I submitted yast2-printer version 2.17.36 to STABLE/FACTORY. It should be available soon via the opsenSDUSE build service at http://download.opensuse.org/repositories/home:/jsmeix/ -- 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 mschmidkunz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443676#c3 --- Comment #3 from Martin Schmidkunz <mschmidkunz@novell.com> 2008-11-21 03:30:43 MST --- I think that our discussion yesterday showed that we had two different models in mind. The solution of this issue involves a bigger discussion which should be started after the release of SLES 11. -- 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#c4 --- Comment #4 from Johannes Meixner <jsmeix@novell.com> 2008-11-21 04:10:43 MST --- See the related bug #446508. -- 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#c5 --- Comment #5 from Johannes Meixner <jsmeix@novell.com> 2008-12-02 01:13:08 MST --- For the log what the "different models" in comment #3 means: Currently the YaST dialogs with a tree at the left where clicking different tree items results different dialog content on the right are implemented via the YaST module DialogTree. Unfortunately this module does not implement a tree of separated dialogs which I need but one single dialog with different tabs where the tabs are accessible via the tree items which I do not need. Unfortunately the layout on the screen does not show that it is one single dialog with different tabs because there is not the usual tab label style of a usual tabbed dialog, see for example http://en.wikipedia.org/wiki/Tab_(GUI) In contrast what DialogTree results looks exactly like separated dialogs which are accessible via a tree. This leads to maximum confusion: For me because I had to implement special tricks in my code to let the single dialog with different tabs behave like a tree of separated dialogs which I do need. For the users because it does not work as it looks like (looks like a tree of separated dialogs but works as one single dialog with different tabs). -- 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 mschmidkunz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443676#c6 --- Comment #6 from Martin Schmidkunz <mschmidkunz@novell.com> 2008-12-04 05:10:15 MST --- I agree with you and now I know what HuHa meant by complaining about the misuse of trees. My point is, that currently there is no widget which allows to display a larger amount of separate dialogs. Not to mention the restrictions we need to take into account due to ncurses 80x25 layout. If you have any suggestions which widget to use instead of tree widget please let me know. -- 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#c7 --- Comment #7 from Johannes Meixner <jsmeix@novell.com> 2008-12-04 06:15:38 MST --- I think when I need separated dialogs, I have to implement separated dialogs. I will experiment with a global data structure which holds the current values of the navigation tree so that it is available in all separated dialogs. In each of those dialogs I display the navigation tree on the left and on the right the actual dialog content so that it looks like what DialogTree currently shows i.e. separated dialogs with a navigation tree. If this works for me, then DialogTree can be fixed so that it shows what it actually is i.e. a single dialog with different tabs. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com