Re: win32event.WaitForInputIdle() returns too soon
- From: "Hans" <NoSpam@xxxxxxxxx>
- Date: Fri, 29 Jun 2007 22:03:12 +0200
"Gabriel Genellina" <gagsl-py2@xxxxxxxxxxxx> schreef in bericht
news:mailman.184.1183090500.22759.python-list@xxxxxxxxxxxxx
En Thu, 28 Jun 2007 19:15:40 -0300, Hans <NoSpam@xxxxxxxxx> escribió:
I'm sending keyboard and mouse events to a seperate windows application.
I use win32event.WaitForInputIdle() before calling e.g.
win32api.keybd_event()
However it seems that WaitForInputIdle() returns too soon because some
of my
events get lost. Now I'v created my own WaitForInputIdle() which calls
From the Microsoft docs for WaitForInputIdle: "The WaitForInputIdle
function only works with GUI applications. If a console application calls
the function, it returns immediately, with no wait."
A typical Python script is a console application.
--
Gabriel Genellina
It would explain my problem.
Perhaps I could create a small windows application as interface..
I have to think about it ( and wait, as I currently don't have access to
visual C++, nor the MS documentation)
Thanks,
Hans
.
- Follow-Ups:
- Re: win32event.WaitForInputIdle() returns too soon
- From: kyosohma
- Re: win32event.WaitForInputIdle() returns too soon
- References:
- win32event.WaitForInputIdle() returns too soon
- From: Hans
- Re: win32event.WaitForInputIdle() returns too soon
- From: Gabriel Genellina
- win32event.WaitForInputIdle() returns too soon
- Prev by Date: ORM layer
- Next by Date: Re: win32event.WaitForInputIdle() returns too soon
- Previous by thread: Re: win32event.WaitForInputIdle() returns too soon
- Next by thread: Re: win32event.WaitForInputIdle() returns too soon
- Index(es):
Relevant Pages
|