m theo

You know, this was probably beaten around ages ago, but I couldn't figure out how to search for it effectively.

I'm working on a patch. I change some stuff. I inadvertently or advertently hit cmd-w. (After all, it's right next to cmd-e.) Max closes my patch--without first asking me if I'd like to save my changes.

This (lack of dialog-boxing) behavior is different from pretty much every other app I use in daily life.

What is the rationale for not asking the user if he/she would like to save changes?

You know, this was probably beaten around ages ago, but I couldn't figure out how to search for it effectively. 

I'm working on a patch. I change some stuff. I inadvertently or advertently hit cmd-w. (After all, it's right next to cmd-e.) Max closes my patch--without first asking me if I'd like to save my changes. 

This (lack of dialog-boxing) behavior is different from pretty much every other app I use in daily life. 

cmd-w-no-prompting-to-save-changes

sounds like a bug to me. Sometimes my patches don't show the "dirty bit" in the window (on XP it's an asterisk next to the patch name if it's been changed). Save, close, re-open and it's OK again. Haven't seen that in awhile though.

also I hardly ever use control-E, I just hold control and click on an empty part of the patch to lock/unlock :)

It should prompt. Feel free to send a report to support.

cmd-w, no prompting to save changes