Hi Minchia,
It always helps to include the code near the problem. Several suggestions were offered for your previous thread, we don't know what you ended up with.
Intermittant problems or problems that go away when you run in debug usually indicate a timing problem. The script is getting ahead of the application. Adding wait statements can help you find where the timing problem is.
There is a trace selection in the debug menu that will step through the code at a pace you select and show how variable values are changing in the watchlist.
What is the title of the obscured window? Is it the same as the dialog you are attempting to send the alt-o to?
If you have a SetFocus for the dialog, precede it with a WaitWindowOpen statement. Errors and strange things can happen if the window is not ready when you do a SetFocus. That is because you are bypassing program edits and interfering with the program.
This should provide the necessary waittime.
Code: Select all
WaitWindowOpen>Open Pro-Planner MSG Attachment
SetFocus>Open Pro-Planner MSG Attachment
//send the keystrokes to the window
//Alt-o is the same as clicking the "Open File" button
If you are doing a MouseMove and a click, add a wait statement after the MouseMove so you can see the cursor.
Hope this gets you going again,
Gale