Add "Discard any changes" button to toolbar / menu, which may either use a popup confirmation, or allow users to undo this action if they see they didn't mean to press this button (in which case, again, you must make it obvious to the user what just happened - for example providing an infobox popup or splash screen, etc.).When doing this, present a non-interactive splash screen "saving changes", so that the users can learn that whenever they close the application all changes are saved automatically. On exit, save the changes automatically (without any confirmation dialog - people are notoriously bad at clicking the right button in a confirmation box, especially after they've seen it a few thousand times).Which is why the best course of action would be to emphasize to your client/boss the necessity of Undo/Versioning functionality. The possibility of mistake is aggravated in this case because there is a similarly labeled "Exit with saving" button right next to it.Īs I understand, in your case you have an application where losing one's work can have disastrous consequences. Having "Exit without saving" button is dangerous, even if it can be sometimes convenient.
This is why all buttons that perform "dangerous" actions come with a confirmation popup.
Now as for other possible buttons, you must understand that there is always a possibility for someone to click that button by mistake. There is generally no need to add extra "quit" button to the toolbar. It is expected that Close button should always be present in the UI - usually in the form of the little "x" button in the top right corner (or top left if you're on MacOS). Should there ever be a button on the UI to bypass these prompts?Īny help justifying these standards would be much appreciated :) Thanksĭownload bmml source – Wireframes created with Balsamiq Mockups.Should Exit and Save/Exit without Saving ever be merged in software?.Should Exit/Close buttons ever be put on the UI when they exist on title bar/file menu etc?.I've seen discussions on never merging the Save and Exit functionality and I believe bypassing this prompt completely goes against any good UX practices! There is no undo functionality or versioning so this prompt is our only safety net in discarding changes. I can't justify putting something that destructive on the UI, after all we aren't simply writing yelp reviews here! They requested I add a "Exit with Saving" and "Exit without Saving" button to our existing toolbar which would bypass the prompt.
GEARCITY SAVE ON EXIT WINDOWS
I believe I know the correct answer but this is what I'm dealing with, I'm working on a windows application and someone raised an "issue" of being prompted when closing the window to Save/Don't Save/Cancel (only if changes were made) pretty standard right? if you make a change you should prompt the user when closing if they really meant to close with/without saving their changes, after all this is for a medical application where doctors spend hours writing a diagnosis/resulting! what is the best practice for closing a window and saving? Being we have a title bar/file menu/toolbar etc. This has been discussed a few times on here for web implementations but never for a desktop application.
0 kommentar(er)
