AutoHotkey Community

Insight needed. Is the "Gui, New" command now required if using named GUI's? The documentation suggests it is needed to insure "Gui, Add" statements work correctly. Does it provide any other benefit?

Can someone provide a simple code example showing the creation of a named GUI window using this command?

Thanks,
TL

"Gui, New" isn't really required for most cases. However, it does allow you to make unnamed GUIs (which is different than the Default GUI functionality, which is "GUI, 1" to begin with). This allows you to create GUIs - for instance in a function - that won't use up the GUI Namespace. You can reference them by their HWND:

_________________

Recommended: AutoHotkey_L
Basic Webpage Controls

Not at all.
I suppose you're referring to this:

I think you misunderstood. The intent of that statement was to make it clear that Gui New is not mandatory: you can just use Gui Add, and the GUI will be created automatically.
One common error when creating a GUI inside a hotkey subroutine is assuming that the GUI didn't already exist, even though it wasn't destroyed since the last time the hotkey was pressed. Typically the end result is an error message saying that a Gui control variable is already in use. If you always begin with Gui Name: New, this won't be a problem - the old GUI will be destroyed automatically.

Some users thought that setting the title when creating the Gui was more logical than doing it with Gui Show. Gui New allows this.

However, the main purpose of Gui New is to create an unnamed GUI, as jethrow demonstrated.

Thanks jethrow and Lexikos. A concise, clear, complete, and quick response. Very much appreciated.

Lexikos, and everyone who helped, thanks for all of the new AHK functionality. As a programmer (aren't we all), I can appreciate the talent and time applied to this project.

TL