Adding a Confirmation Screen before closing a Max Application

Hi Narner,
Yes! You can do this, but the approach is a buit "hacky" as you have to edit the 'maxinterface.json' in your standalone (its in the ./resources/interfaces).

This is what I have done:
1. In my patcher i have [receive my_quit] that when it receives somthing it opens the "are you sure" dialog etc...
2. In the maxinterfaces.json, an the "menus" section, I added an entry like so:

{  
    "message" : "mycustomquit",  
    "label" : "Quit",  
    "navkey" : "x",  
    "target" : "my_quit",  
    "shortcut" : "Q" 
}   

There is a "quit" entry already, that max uses. You can just copy that and change the message and the target. The key to this whole thing, is that the "target" if set to somtheing other that the keywords that max uses, like in this case "my_quit", when this menu item is selected, it sends a bang to any [receive my_quit] in your patch.

3. Also in the "menus", assuming you have a [menubar] in your patcher, find the "customfilemenu" entry. If you replace the "quit" with "mycustomquit", in the actual menubar the entry you see and click, will be yours and not the normal "quit".

This should send a bang to the [receive my_quit], and from here on, you can do your thing! But know you are also responsible from closing max, which can be done with a " ;max quit " messabox.

I have done this and works fine, but it is a good strat to also disable the "X" button on your standalone (form the [standalone], check the "Cant close top level patcher"), as there is no way (trhat i know of) to override its behaviour from max, so there will be no "are you sure" prompt, only if the user has to go through the menu.

Hope this helps!