Radio variables still in memory after Gui is Cancelled and Destroyed

Report problems with documented functionality
pneumatic
Posts: 299
Joined: 05 Dec 2016, 01:51

Radio variables still in memory after Gui is Cancelled and Destroyed

13 Jan 2017, 04:50

Code: Select all

Gui, Cancel
Gui, Destroy
After calling the above, the associated variables of any radio buttons in that GUI are still in memory....[/snip]

edit: nevermind, this is a good feature to have.
Last edited by pneumatic on 13 Jan 2017, 04:56, edited 1 time in total.
just me
Posts: 7303
Joined: 02 Oct 2013, 08:51
Location: Germany

Re: Radio variables still in memory after Gui is Cancelled and Destroyed

13 Jan 2017, 04:53

Of course the workaround is simple: just set the radio buttons to 0 on GuiClose, ...
It's your GUI, so it's your task. ;)
pneumatic
Posts: 299
Joined: 05 Dec 2016, 01:51

Re: Radio variables still in memory after Gui is Cancelled and Destroyed

13 Jan 2017, 05:00

Actually, now I remember why I thought it was a bug :)
Gui, Destroy
Removes the window (if it exists) and all its controls, freeing the corresponding memory and system resources. If the script later recreates the window, all of the window's properties such as color and font will start off at their defaults (as though the window never existed). If Gui Destroy is not used, all GUI windows are automatically destroyed when the script exits.

Return to “Bug Reports”

Who is online

Users browsing this forum: No registered users and 4 guests