Zugg Software :: View topic - onDisconnect EVENT not firing when CMUD is closed without closing the session.

Posted: Tue Dec 02, 2008 1:21 am

This is not a bug or design feature of 302B alone. The 2.xx versions have the same problem. It would be nice that when CMUD is closed by clicking on the close button, all open sessions fire their onDisconnect Events.

Posted: Tue Dec 02, 2008 1:35 am

This cannot be done. Closing the application requires that everything be immediately terminated. This means no more MUD socket connection to send anything to, and no more database changes or scripts running. It would be too easy to cause CMUD to hang by calling some sort of script that didn't terminate.

If you exit gracefully via File/Exit then it should work. But using the X close button is the same condition that Windows uses when rebooting to terminate applications, and it's critical that closing an application with the X be as fast as possible.

You can always add your own button to your session that performs a #DISCONNECT command and the a #MENU {File|Exit} which will ensure that your disconnect events run before CMUD exits. If you right-align the button, and give it a big X icon, then maybe you can train yourself to use that instead.

In general, it's a bad idea to close applications using the red X button. Train yourself to use File/Exit or whatever else the application offers.