Wait for Window doesn't work for me...

[DarioB]

I'm new to Girder and I'm doing some tests by opening up Notepad and entering text. I have a multigroup with 2 commands. The first one executes Notepad.exe. The second one uses the Keyboard action to enter a text.
This solution does not work unless I use a wait timer after the execute command and before the keyboard action. This seems unstable since any lag in opening Notepad could result in a failed Keyboard action.

The Wait for Window command seems to be the right tool. But I haven't been able to make it work as described in the documentation.
Can anyone please describe, step-by-step, how to set up a functionality that starts Notepad, waits for the window to be active (no matter how much time it takes) and outputs text in it.

Thanks!//Dario

[Ron]

Did you check the checkbox? 'wait for window'

[DarioB]

Did you check the checkbox? 'wait for window'

yes

[DarioB]

Did you check the checkbox? 'wait for window'

yes

...It still doesn't work

[Ron]

Did you target the window that the wait is supposed to wait for?

[DarioB]

Did you target the window that the wait is supposed to wait for?

Yes.

[DarioB]

Every time I run the group the timeout field for the wait command gets reset to 0 (ZERO) which according to the docs results in the command not waiting for the window. Bug??

[Promixis]

Did you click apply after making the changes?

[DarioB]

Did you click apply after making the changes?

Yes.

Maybe someone can write a simple step-by-step instruction (that even I can understand :) ) so that I'm sure I'm doing this in the right way.
Basically I wan't to open up Notepad.exe and write a sentence to it only when the window is available i.e. through the Wait for Window option.

Thanks!

[Promixis]

Okay,

Wait

Enter a timeout value in the box incase the window doesn't start. Something like 3000 (3 seconds).

Target. Find notepad. Only match the class name "notepad".

Click the wait for window box.

Click apply

[DarioB]

Okay,

Wait

Enter a timeout value in the box incase the window doesn't start. Something like 3000 (3 seconds).

Target. Find notepad. Only match the class name "notepad".

Click the wait for window box.

Click apply


I don't understand. If the Wait for windows function is supposed to do what I think it does, entering a timeout value would override the Wait for windows option. This would start the window after 3 secs no matter what, which kind of defeats the purpose of the Wait for window functionality doesn't it?
I would like to have my Girder command flow halt until the targeted window is active even if it is activated after 5 minutes. Only then can I be sure that my commands don't run off to do other stuff before a certain event.
Hope this makes it a bit more clear.

Thanks//D

[JSMain]

I believe the Time out value in this wait for window function actually gives up looking for the window after the time out.

At least I think that is the way it's supposed to operate, but alas, I've had this problem also. Perhaps it's a bug?

[Ron]

That is actually by design. After the timeout Girder will resume processing even if the window doesn't exists. If you don't want that to happen add a 'Window Exists' after the wait and stop processing if the window still doesn't exists.