On 15-05-2019 13:32, Alex X wrote:

On Tue, 14 May 2019 19:44:01 +0200, Mike Wey wrote:

On 14-05-2019 05:10, Alex X wrote:

Any news on this?


It's severely cramping my style ;/

Unfortunately no.

Ok, So I figured you probably don't care enough to invest your time to fix it so I went ahead and looked in to it and was able to get it fixed:

That is indeed partly the case, although i did find an option for win XP
and older.

This seems like an interesting solution, overriding the memory that
holds the original SetWindowsHookExA. That does mean care should be
taken that the size of the replacement function is not to large.