Button not close

[Chris_1013]

I'm probably being dense, but if I have a GUI with Opt("GuiNotifyMode",1) set, can I set a particular button to NOT close the GUI, or will I have to set the notification mode for each button individually?

[jpm]

I'm probably being dense, but if I have a GUI with Opt("GuiNotifyMode",1) set, can I set a particular button to NOT close the GUI, or will I have to set the notification mode for each button individually?

<{POST_SNAPBACK}>

This option will disapear in the next beta just forget

[Chris_1013]

OK, so I've got the newest beta, am I right in thinking then;

All controls notify

None close the GUI

If you want a button to close the GUI you do a WinClose("Gui Title") in the message loop when that button is returned?

[Chris_1013]

If I don't do this, what's the problem? Surely the GUI won't stay on screen until I call a GUIDelete(). Does the GUIDelete() just remove the memory used by the GUI?

Also, I've got the newest Beta installed, but my GUI is being closed by clicking on a button, even without the WinClose() in the message loop... I thought this shouldn't happen now?

[Chris_1013]

OK, so I'll do that then. However, at the moment, my GUI is closing anyway, even when I don't want it to (ie, haven't put in any GUIDelete code or whatever). I thought buttons didn't auto-close the GUI anymore?

Edited September 30, 2004 by Chris_1013

[Jon]

Exiting the script automatically closes/releases all windows

GuiSetState(@SW_HIDE) is used to hide a GUI

GuiDelete() is used to delete and free a GUI

[Chris_1013]

Gotcha, very good. Think I've grasped *that* concept now....

But, how would I have a button on a form that I click and it doesn't close the GUI, just leaves it running.

[Chris_1013]

OK, being dense again, I was exiting out of the message loop (it ain't gonna check for additional button clicks then is it?!)

I'm a wally.