3 ms·
> destructive actions should require a little more confirmation, no? It used to be you had to double-click almost everything if there was a chance of a strong s
by xg15 10y ago
> destructive actions should require a little more confirmation, no? It used to be you had to double-click almost everything if there was a chance of a strong side-effect;
I grew up with Windows 98, so for me the X button would be the baseline that feels perfectly logical and natural. But I want to ty and explain why I think it doesn't contradict the above logic:
I think a long-standing design rule in Windows is that the X button action should have as few side-effects as possible apart from closing the window: Closing dialogs and tool windows typically does nothing except closing the window - and your user expectation is that you can trivially restore those windows if you wanted.
For "Yes/No" or "OK/Cancel" type dialogs, the X button typically maps to the action with the least consequences - i.e. "No" or "Cancel". When all choices have consequences is sometimes even disabled to force the user to make a conscious choice.
In the events where closing a windows has direct, irreversible consequences - e.g. closing a program that has unsaved data - the program is expected to show some kind of confirmation: An "Are you sure" or "Do you want to save?" dialog. So in effect, clicking the X button is even safe in these cases because all that click will do is bring up a confirmation dialog.
All of this requires more effort from the developers of applications, but I think treating the X button as a non-destructive action by default actually gives the user more confidence to explore the UI because there is an obvious way how to safely get back.
- marcosdumay 10y agoI got to use Windows 3 and see it as an improvement over a CLI-only system, and got to edit my X11 configuration for making my monitor don't blow (or at least stop making that infuriating noise out of frequency monitors do - but the documentation was adamant it would blow). I saw the beginning of the GUI spread. Yet, I was never able to make any sense about the Windows double-click required standards. It just looked completely arbitrary, like any action MS wanted to map into a click, but there was an action mapped there already, they made it a double click. I am pretty sure the author is rationalizing that line about side-effects.
- Senji 10y agoI've never encountered a doubleclick outside launching programs, opening files in explorer.
- Senji 10y agoFor example, newest versions of Notepad++ save all your "unsaved" tabs on the fly. They are available when you reopen the program. It's a good UX.