AutoHotkey Community

cornell2 · Joined: 18 Mar 2005 Posts: 166

Though I posted this, buried in another topic, I am posting here because answer might benefit other new GUI function users too.

I have some "parent" script, that is mean to, at certain times, gosub to my GUI form and get some data (so the gui-form should be isolated and consolidated in one subroutine. ie

TeknoMusicMan · Joined: 14 Apr 2005 Posts: 188 Location: Wisconsin, USA

you need to make a button that executes Gui, Submit.

take gui, submit out from where it currently is

The way you have it coded right now, the scrip is adding the 3 "whatevers" to the form then showing the form then imediatly after that submiting the form. So you need to make a button

Gui, add, button, gSubmit, Finished

then have a sub called Submit with gui, submit in it

Submit:
{
Gui, Submit
return
}
_________________

"Make it idiot-proof, and someone will make a better idiot."

Laszlo · Joined: 14 Feb 2005 Posts: 4078 Location: Pittsburgh

try this

cornell2 · Joined: 18 Mar 2005 Posts: 166

Please someone tell me there is a more elegant solution than these kinds of workarounds. I cannot believe that one has to go through all this just to make sure the form completes before returning back to the "parent" part of the script.

(FYI - my real code indeed does have a button at the bottom, with a label that goes to a submit routine ... but this does not keep the form up!)

Incidentally, this is the another source of astonishment, that I always need a button ... ie .. that I cannot have a "form" that submits when the user presses enter. This is the subject of another recent thread (that elicited several interesting workarounds). But I would think that these two issues are rather fundamental and should not need kludgy workarounds.

I am sure there is some basic syntax or other lack of understanding on my part (or hoping).

Thanks!

cornell2 · Joined: 18 Mar 2005 Posts: 166

FYI ... to clarify (I am trying not to post a lot of specific gui code yet, in order to keep things simple)
--- my script looks like

Laszlo · Joined: 14 Feb 2005 Posts: 4078 Location: Pittsburgh

GUI is a new thread, spun off from the main line of your script, with its independent life. Most of the time this is what you want. Especially, if you bring it up in response to a HotKey. InputBox is the sequential variant, though less flexible than a GUI. You could also store the window ID in a variable after the GUI is shown, and WinWaitClose in the main line of the script. It is only two extra lines of codes. Why is it so bad?

cornell2 · Joined: 18 Mar 2005 Posts: 166

OK - sanity check for me ...
Below is a little snip of some code I have ... am I wrong or should this stop and ask me for a Price ... ?
when I run it ... it displays the form and goes to the msgbox and exits without ever letting me input data.

Laszlo · Joined: 14 Feb 2005 Posts: 4078 Location: Pittsburgh

As I said, the GUI lives as another thread, the main line of your script goes on in its own world. You really want InputBox here, or the extra two lines from my previous posting.

cornell2 · Joined: 18 Mar 2005 Posts: 166

Your solution seems to work, so I am happy. For the record - what I find counterintuitive is that the "new thread" scenario - is generally not how the rest of ahk scripting works. Not that it is bad ... but since most of the other functions don't rely on this useful technique, you sort of have to glue them together with a little duct tape (my visual description of these workarounds). But I'm happy it works, and also just love ahk so I can't really complain.

And thanks all - this board is an amazing resource - with very supportive and responsive members.

cornell2 · Joined: 18 Mar 2005 Posts: 166