Wait for Window checkbox

[MatB]

Well, maybe this is a stupid question, but i can't make it work.
It seems to me that the "Wait for window" option doesn't work well.
In fact, when i open a window - let's say, notepad - wait for it, and send a keystroke, the key won't be
received unless notepad is enough cached to run immediately. It's like if the keystroke is sent when the
message queue for that window is not empty.
Nobody sees it?

[Ron]

Did you also specify a timeout ?
I know that is not quiet obvious but
if you leave it on 0 girder will timeout
after 0seconds and thus never wait for the
window.

-Ron

[MatB]

Uh, i was thinking that "Wait for window" stays for "Wait until the window can accept a command". As i understood, it's simply a delay. Isn't it?
My computer is quite poor of memory, swaps much, so i'm experiencing big lacks in the macros execution, like application windows still open after the end of the macro, keys unreceived or sent to other apps - really not nice. A fixed delay is difficult to use, since it can vary up to seconds. Buying some megs is out of question.

It seems really strange to me i'm the only experiencing this.
Again, i'm not sure i've understood how the thing works.

[Ron]

No Wait for window waits until girder sees the window popup in the window-list. Usually the window is also ready to accept input at that stage but nothing is garanteed.

The timeout, is just a maximum time that Girder waits for the window to appear this to prevent Girder from deadlocking here.

-Ron

[MatB]

Ah.
So, if i set an high timeout, and the thing goes ok, i won't be waiting all that much. Good, i'll try.

[dpeters]

Put another wait right after the 'wait for windows' command of about 100 milliseconds. This will give the program enough time to initialize after the window pops up.