Quote:
Originally Posted by Rev. Bob
Fully agreed. The situation I'm running into is where I've hit "save", the program has returned control to me (usually an indication of success, but in calibre's case an indication that the Save Job has started), and since I'm done, I try to close the program. I'm most emphatically NOT using "close program" to reach a save dialog.
And in my biased opinion, "close after X" should not close if X generates an error. In that scenario, the program should abort the "close" instruction and instead display the error, so the user has a chance to react to it. I don't think that's an outrageous or even unusual request.
Heck, I'd even be happy with a way to disable "close when done" entirely in the preferences - set it once instead of being vulnerable to slip-ups Every. Single. Time.
|
Hmm, I think I see what you mean. FWIW I don't believe "close when done" should be an option in the average UI toolkit (together with Save and Exit).