https://bugzilla.novell.com/show_bug.cgi?id=217368 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #2 from bluedzins@wp.pl 2006-11-04 03:12 MST ------- Created an attachment (id=103777) --> (https://bugzilla.novell.com/attachment.cgi?id=103777&action=view) y2 logs Here we go... However I doubt there is anything in the logs. Simply -- cancel should cancel ;-) changes. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=217368 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |ms@novell.com -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=217368 ------- Comment #4 from bluedzins@wp.pl 2006-11-14 06:44 MST ------- Marcus, don't you think that this report is linked too far? Now it is a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=219946 but I see no relevance -- the other one is about crashing, here there is no crash at all. Just "reversed" meaning of cancel button. It has nothing to do with hardware, crashing, just design flaw. Cancel should revert changes. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=217368 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | ------- Comment #6 from bluedzins@wp.pl 2006-11-14 11:42 MST ------- No, no, nothing crashed. There is no installation either :-))) Look, you work with your suse for a year, ok? Now, you want to try out something new. So you decided to change res from 1024x768 to 1280x1024. You set it (yast2 -- module graphics card & monitor), test it, everything is _fine_. No crash. After testing yast2 asked you if you want to save it -- yes. But... you are still in this module and you have still to click accept or cancel. .. You changed your mind, on the last moment, you clicked cancel. What to do you expect? Will res be changed? Well, unfortunately -- yes. You clicked "cancel" to cancel all the changes, but the changes were applied before and on your next reboot the system will use the new, canceled settings. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=217368 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|bluedzins@wp.pl | ------- Comment #8 from bluedzins@wp.pl 2006-11-15 03:16 MST -------

If I sax no I'm still in sax. Ok at that point there is a ok button to be able to repeat the complete procedure and a cancel button to exit sax. But this cancel button couldn't revert the already written configuration. I thought this would be clear as you intentionally clicked on "save" some time before

As I said -- it is design flaw -- there are to many points for "accepting". In this situation "cancel" does not mean cancel, but rather "commit". It is bad (to redefine words). My suggestion: * if OK means test it should be named like this --> "test" * if cancel means close it should be named like this --> "close" * there should be cancel button anyway named... well, cancel :-) and it should be able to revert changes, after all you have undo in text editors which can cancel last changes even if you saved your file on disk. And when you get back from Sax there should be no such dialog, you are just back to the graph.card module dialog. Then you have three crystal clear choices -- close the thing, cancel changes or test something more. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=217368 ------- Comment #10 from bluedzins@wp.pl 2006-11-15 04:51 MST -------

I'm sorry but it's really funny to hear exactly what exists some years ago.

That's good :-)) Thanks for the reply, but I still think redesigning (1) and (4) would provide more useful module. Reasons: ad.1) it is bad design to provide button for action with unclear destination. "OK" in common usage means "ok, accept changes and close the dialog". But here the meaning is changed (really bad). What's more -- the user see the dialog with more options. The user has no chance to anticipate the options from looking at "ok" button (so it is pretty meaningless -- it could be named "ha!" ;-) both versions doesn't tell a thing where they are going). ad.4) answering "exit" has no value added (without this dialog&question you would simple click on "close" button), answering "stay" has no value either :-) because without this dialog the question is irrelevant. It is no shortcut (more precisely: quite opposite for scenario "stay"), it doesn't clarify anything... You can draw a graph -- each node would be a button, any arc would be an action. Then you could spot that easy tasks like "ok for changes" are complicated (number of nodes) and some like "cancel" are impossible to do. And see how many redundant paths are there.

By the way are you software developer

Yes:-).

I will set that to later because it's definitely too late for 10.2

Ok, I would be happy to see it in further version, not necessarily in 10.2. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=217368 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=217368#c12 --- Comment #12 from Stephan Kulow 2008-06-25 03:41:24 MDT --- mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) -- 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=217368 User ms@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=217368#c14 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |sndirsch@novell.com Status|REOPENED |NEW --- Comment #14 from Marcus Schaefer 2008-06-25 03:55:41 MDT --- Stefan if you have plans to make changes at the GUI you might want to take this into consideration. Feel free to close if you don't plan to change anything there -- 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=217368 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=217368#c16 --- Comment #16 from Stefan Dirsch 2008-06-25 04:29:59 MDT --- I don't plan to change this behaviour. -- 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.