On 08/03/2009 05:12 PM, Martin Nordholts wrote:
> On 08/03/2009 11:04 PM, gg wrote:
>> As I said in my original post , this is not a "by the way the image
>> was not saved" it is an error condition what warrants an modal dialogue
>> and a user response.
> Please let's not bombard the UI with modal dialogs. They are excellent
> for interrupting workflows and annoying users. The proper solution is to
> make changing the comment dirty the image, it is not to show a modal
> dialog when the image is not saved.
> / Martin
I appreciate your thinking on this and what you suggest in this
particular situation is a great way to deal with that specific case.
However, I would like to point out that if a user _intends_ to save the
file because the _user_ believes a change has been made, then should not
the user be notified that either a) the user is incorrect and no change
has actually been made [and thus the user probably needs to do something
that the user has failed to realize has not been done], thus the file is
not going to be saved OR b) the program is incorrect in thinking that no
change has been made (as was the case in this situation).
_I_ would want my "workflow interrupted" if the program was not going to
do what I had asked it to do. Maybe that's just me.
As long as the focus in the modal dialog is on the dismiss button, then
it is easy enough to hit [Enter] and it goes away.
That would be my preference.
Gimp-developer mailing list