5 ms·
If a user has the habit of frequently quitting the program with unsaved changes, with their brain clicking through the "discard changes?" dialog in auto-pilot m
by kazinator 4y ago
If a user has the habit of frequently quitting the program with unsaved changes, with their brain clicking through the "discard changes?" dialog in auto-pilot mode, it is next to impossible to distinguish that case from a situation in which it was done without intent, causing unwanted loss of data.
I suspect that a simple UI modification which could reduce occurrences of the situation, without being too obtrustive would be to make it a checkbox:
[ ] I agree with unsaved data being discarded [ OK ]
The OK button is ignored unless the box is checked. This is exactly like a Terms-of-Service agreement workflow.
Another idea would be to make the UI sensitive to the amount of unsaved content. The software should have an idea of whether the unsaved content represents 57 edit operations, or just two. Or maybe in terms of number of objects or bytes involved or some other specific measure.
If the amount of unsaved material seems significant, then have the checkbox workflow. Otherwise just the [OK] without the checkbox.
- kortex 4y agoTFA sort of addresses this and while it's better, it's still "warn-think", it's just a more glorified and tedious habit, depending on what happens when OK is clicked without the discard box checked. I presume the default action stashes the data somewhere, in which case it's basically the trash bin pattern or tempfile pattern (stored durably, not /tmp), and we can safely go back to a plain dialog like: You have unsaved changes. Do you wish to save as a new file, or discard? (Unsaved changes can be recovered for 1 month before permanent deletion)
- kazinator 4y agoIf unsaved changes can be recovered for a month, then why mention it every time. Just let the user quit without any prompting.
- dspillett 4y agoA further option is to do what Notepad++ does: save current state even through closing and reopening the application until the user closes the file. When you restart the app files that were never saved and never close are as they were, modified files too. The possible issues with modified files is that if you think you've saved and don't get prompted then run some other tool that relies on the new information it won't be there (as the saved state is elsewhere, not the main file). Keep the “do you want to save first?” prompts for when closing the file. Of course for some file types this could use a lot of storage, so it won't be as applicable everywhere.
- bombcar 4y agoBut this type of idea would be disastrous when applied to private browsing windows, for example.
- Jtsummers 4y agoNothing about what's being discussed has been presented as an absolute. So in situations like that, just give a warning, if anything, since saving might be counter to the intent of the mode. In other words, exercise good judgment based on the circumstances.
- bombcar 4y agoEven there a warning can be annoying - as often a private window needs to close very quickly.
- Jtsummers 4y ago>> So in situations like that, just give a warning, if anything [quoting myself, adding emphasis] Again, it's about judgement for the circumstances. We're in agreement here, but your original comment read as if you were taking the discussion here as being about absolutes.
- dspillett 4y agoCorrect. Nothing like this should be enabled in a private mode, and no user should expect it to be¹ enabled in a private mode. Losing unsaved data is a logical consequence of being in a private mode, it is up to the user to be careful here. This won't harm unsuspecting users if you need to explicitly request privacy, by for instance opening an incognito window, if you request privacy it is valid to assume you know the potential consequences. ---- [1] Though you shouldn't rely on it not being, never assume there are no idiots around not thinking straight when implementing private functions and things that might interact with them! Trust but verify. Or just verify.
- smegsicle 4y ago
- chongli 4y agoIf a user has the habit of frequently quitting the program with unsaved changes, with their brain clicking through the "discard changes?" dialog in auto-pilot mode, it is next to impossible to distinguish that case from a situation in which it was done without intent, causing unwanted loss of data. This problem was solved in MacOS X Lion 11 years ago. The solution is to get rid of this dialog entirely and to simply auto-save documents by default when quitting and to re-open all documents when the application is started again (persistent state). This feature applies even to new documents which have never been explicitly saved by the user nor even given a name. Only when you attempt to close (or explicitly save) an unnamed document does it ask you to choose a name or delete the document (with an explicit delete button marked in red text). This also has the added benefit that when you use the save command (command-s) you're actually saving a snapshot of your document which you can recover later with a time-machine like history viewer interface. Otherwise, all other changes to your document since the last snapshot are auto-saved.
- chopin 4y agoNotepad++ does it the same way which I quite like.