🚀 go-pugleaf

Bob Gonder <notbg@notmindspring.invalid> wrote:
>Anders Johansen wrote:
>
>>The code below has a potential flaw: The callback code is 
>>running in the main thread, and so may block the system event
>>processing or at least delay it.
>
>The only slow part in the hooks I can see is notifyKeyDown,
>and it's reliance on virtual KeyDown functions.
>Everything else should be quite fast enough.


Good suggestions!

The problem is however that if you include this code in a program that blocks the message processing loop (say, by doing while (true) {};) the system temporarily becomes unresponsive, as the callbacks are blocked from executing for some reason. This happens even if no observers are registered. This is why I expect that moving the event processing etc. to another thread is a Good Idea.

Of course, this introduces a risk that the event handlers could be run outside the main thread, which would create problems with VCL code I expect.

Therefore my idea is:

* Place Hook code in separate thread
* Convert events to window messages sent asynchronously to the main thread (or some other way to avoid threading issues in VCL).

Anders



A