WinWait not Catching Correctly

[kjcdude]

On about 5% (20) of the computers i run my script on winwait doesn't catch a certain window that is clearly visible.

If i open notepad and save a file with the exact name on the window active it catches it and moves onto the next step.

I'm able to repeat the error, though on different pcs. There's no reason as to why it's happening or why it isn't happening on certain pcs.

Has anyone else experienced this weird bug?

[Jos]

Have you verified the the window information with au3info to see if its really correct ?

[raer]

Sorry, my mistake. I thought you were talking about RunWait. :-(

Yes. I think it's problem of particular programs. Some of them do complicated actions before they really starts (I think I had this problem when trying to wait for end of the Rollcage game) like running different process and terminating the original one - here it is a possibility to find out which process runs until the program has changed and then use ProcessWaitClose function. Or when they restarts (Portable Firefox/Thunderbird when updating), the scripts recognizes the program ended but don't care that they started again (which is correct behavior, though a little bit confusing).

I think the simplest "solution" will be to use some message like "Press OK after the program has ended" like Total Commander does.

Edited January 16, 2008 by raer

[kjcdude]

Have you verified the the window information with au3info to see if its really correct ?

I have actually, i even copied pasted the window text back into the script for safety.

[ocoro02]

On about 5% (20) of the computers i run my script on winwait doesn't catch a certain window that is clearly visible.

If i open notepad and save a file with the exact name on the window active it catches it and moves onto the next step.

I'm able to repeat the error, though on different pcs. There's no reason as to why it's happening or why it isn't happening on certain pcs.

Has anyone else experienced this weird bug?

Yep - I see the same kind of thing. I tend to use WinWait (I figure it makes more sense than 'WinWaitActive' as it should in theory prove to be a catch-all?). I've seen this in particular with certain steps of installing Java JDK 1.5.x and TortoiseSVN.

It also seems to fail more when I'm clicking around elsewhere when an install is taking place - I know this probably isn't a great idea but so long as the windows are existing, I don't see why this shouldn't work ok.

[Bowmore]

I have actually, i even copied pasted the window text back into the script for safety.

I always use the following method cheking that a window is ready for accepting input and I have never had any problems with my scripts which are run on lots of different PCs.

WinWait("My Window", "")
    If Not WinActive("My Window", "") Then WinActivate("My Window", "")
    WinWaitActive("My Window", "")

[kjcdude]

I always use the following method cheking that a window is ready for accepting input and I have never had any problems with my scripts which are run on lots of different PCs.

WinWait("My Window", "")
    If Not WinActive("My Window", "") Then WinActivate("My Window", "")
    WinWaitActive("My Window", "")oÝ÷ Ûú®¢×¢»aÊ'z)éj»bréZ®'h׭趰whÂ+rدzç¢Ø£ºËgyçm¢IèÂ'âµìb²Û-éäYbµ«­¢+ÙÝ¥¹Ý¥Ð ÅÕ½ÐíµäÝ¥¹½ÜÅÕ½Ðì°ÅÕ½ÐìÅÕ½Ðì¤)Ý¥¹±½Í ÅÕ½ÐíµäÝ¥¹½ÜÅÕ½Ðì°ÅÕ½ÐìÅÕ½Ðì¤)ÁɽÍͱ½Í ÅÕ½ÐíµäÁɽÍ̹áÅÕ½Ðì¤

[GEOSoft]

Try setting Opt("WinTitleMatchMode", 2) to trap any variation you don't notice in the window titles. I don't know why this would vary between machines but you must also be aware that Window Titles are case sensitive.

[NoTolerance]

I just had a similar problem in a script I wrote. I was able to work around it by adding Sleep(3) right before the WinExists option.

WinWaitActive("Software License Agreement")
SEND("!y")
Sleep(3)
If WinExists("Choose Destination Location") Then
    WinWaitActive("Choose Destination Location")
    SEND("!n")
EndIf