Yes/No/Cancel causes Aspirin sales to soar (2007)(martin.kleppmann.com) |
Yes/No/Cancel causes Aspirin sales to soar (2007)(martin.kleppmann.com) |
There’s no ambiguity there. The user is very well-informed that they’re about to quit and lose the document they were working on.
Red "Delete" on the far left, then on the far right a gray/neutral "Cancel" button, and an orange (the app's primary color) "Save"
The same update (Lion?) ruined saving overall. Apple has insisted that apps should never have a "save as." You can hold opt to do it anyway, but it silently overwrites the original too. Maybe or maybe not lets me revert, and idk where even those revisions are stored. Apple might've hoped this catches on, but again nothing else does it this way. I get they want me to duplicate the file first, but no, I already made changes that I want to save-as, it's too late to duplicate.
If they were going for blurring the line between memory and disk, that didn't work either because there is still the concept of saved vs unsaved changes (that can get "deleted"). It's not like Google Docs.
I agree about Save As…
Maybe that could have just been updated to “Save a Copy” or something like that. I don’t really understand why it’s a hidden option.
In some instances this could be a file on disk. But it does not have to be.
I could go full nerd and call it "non-volatile storage" but nobody wants that.
This was heresy at the time, but turned out to be the native user flow for iOS later on. And now it's common in web apps.
https://www.amazon.com/dp/1118766571?lv=shuf&channelId=500&p...
Annulation lever activated!
Do you wish to continue?
Engage STOP lever to continue. Engage CONTINUE lever to stop.
Time remaining 5..4..3...
https://learn.microsoft.com/en-us/windows/win32/api/winuser/...
On a different note, never underestimate the value of a modal dialog that gives you a chance to retry an IO operation that failed. Loose USB cables and network shares over Wifi can make those happen a lot more often.
My understanding today is that one of them(fail?) gives the application a chance to do something clever. Did any application actually handle this gracefully? Something like, Disk 11/15 error(fail) Please put in recovery parity disk.
2. Still better than "Yes, Ask me Later" dialogues that are so insulting to users.
--------
[1] Or the BBC, or whoever, a great many are guilty of this sort of thing.
enum DoesUserWantToSave {
Yes,
No,
Cancel,
}
This is even more true of HN users than it was on the actual playground.
_______________________
| Error. |
|_____________________|
| |
| Unknown Error |
| |
| (Continue) |
|_____________________|Sometimes it is worth the effort of going through and changing the logic elsewhere to keep the boolean positive, sometimes that would be too much effort to retest at the time.
Another option I like, when I have a config object interpreting things so I'm reading doing `if (config.IsWhateverThatThingIsEnabled)` then I can just have paired properties to pick from when I want to check IsEnabled or IsDisabled.
I've come across code where there is an overide for an option to disable something and the naming plus the logical not really make you think about what is happening…
if (!OverrideDisabledOptionToBlockAction) {}Let users have complicated things. You know, moderately complicated. They may not all have degrees in Complicator Science but they should at least grasp the concept of a three-way choice, and if some users find that an unnecessary complication then they can go away and stop trying to use devices.
35 years latter we live in a different world where you can assume an unlimited fast data connection to a data center. Saving and allowing undo is possible today.
Also the minimum Word document is far larger than 2KB. IIRC it's about 10x that size for an empty Word document (docx).
This lets you throw away and start over, but also gives you infinite undo even after "loading" an older version.
The Delete button is shown, and correct, for new files that have not been saved at all yet.
Weird thing is with the setting disabled, quitting TextEdit with multiple new docs open asks if I want to "delete and quit," but Numbers only lets me "save and quit." Even if I press that, Numbers reopens those in a still-uncommitted state. So from all the CSVs I've opened in Numbers and messed with, I have literally 100 pending docs and can only get rid of them by clicking through every single one.