| View previous topic :: View next topic |
| Author |
Message |
Beastmaster Guest
|
Posted: Wed Mar 31, 2004 10:11 pm Post subject: WaitReady ? |
|
|
WaitReady = 1
| Quote: | | WaitReady suspends script execution until the foreground window has finished processing mouse, keyboard, show window, and optionally, paint events. Issue 1 to include paint events, and 0 to exclude paint events. This command can therefore be used to wait until the active application is ready to receive keyboard and mouse events in most situations. |
HotTopic !
I'm currently running a script on an VB application which is connected to a DB via a network. Its performance varies badly so sending strings to forms which haven't been finished to appear ...  |
|
| Back to top |
|
 |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10464
|
Posted: Wed Mar 31, 2004 10:41 pm Post subject: |
|
|
| I think even if you send keyboard and mouse events to a busy window, they will be buffered in that window's thread msg queue. Therefore, they won't be lost. So I don't see much use for such a feature unless there are specific examples you can list. |
|
| Back to top |
|
 |
Beastmaster Guest
|
Posted: Wed Mar 31, 2004 11:12 pm Post subject: |
|
|
Well there's no WinWaitOpen (aka "Window has finished to appear"), and you're right a WinWaitActive won't stop the script to send data into the memory (a black box).
So entering data on seperate moving forms of a Billing plattform without the necessary visibility (for security reasons) isn't something which I can explain to my boss, or even colleagues, as an alternative
Cause that process is running 24/7 I need to have a slight chance to recognize if something is going wrong. Visibilty isn't something to ignore - but maybe I'm wrong and should ask Stevie Wonder or Ray Charles what they think about it  |
|
| Back to top |
|
 |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10464
|
Posted: Wed Mar 31, 2004 11:42 pm Post subject: |
|
|
It's an interesting idea. There is an API function WaitForInputIdle() which "waits until the given process is waiting for user input with no input pending, or until the time-out interval has elapsed".
Do you think this item has enough usefulness and mass appeal to add to the to-do list? |
|
| Back to top |
|
 |
|