> The real bug is that the thread still receives the message even though
> it has timed out on the sender side. The message should be cancelled
> in that case. I'll have a look at fixing that.
This will fix the 'bad key-press' event bug... But it will still mean that
the game will miss a keyboard
Lionel Ulmer <[EMAIL PROTECTED]> writes:
> If it's normal for the sending to time-out, we should replace this code and
> add some HeapAlloc on the sender side and some HeapFree on the receiver side
> each time such a structure is sent ... Which will be a bit problematic for
> performance, but well
Hi all,
While debugging GeneRally (a very nice game), I got some problems with
DInput receiving spurious events (basically, as if key '0' was pressed).
This is traced to the following problem :
In windows/input.c, the function 'queue_kbd_event' stores the
KBDLLHOOKSTRUCT structure on the stack a
