@DiodorS So we have this issue Open in our bug backlog. This weekend, I took a look at what it would take to sort it out. Unfortunately a blanket change to GetKeyState is not a safe thing to do. There are about 50 instances of direct calls to GetKeyState and GetAsyncKeyState, about evenly mixed, and from a casual survey of those calls, it's clear the original authurs had reasons for using deliberately one function or the other. Furthermore, there are ~ 6 additional code paths that abstract GetKeyState or GetAsyncKeyState into generic functions which are then abstracted into various utility function that are used all over the code base. So the implications of making such a change are unknown and risky. Things like using the ecsape key to cancel gestures may stop working, for example. I then looked into seeing if I could spot the specific code that trapped the ctrl key while the laggy brush waas painting, and while I can see the WM_KEYDOWN event, I cannot see which functions are calling GetAsyncKeyState while the paint stroke is being generated without adding a bunch of debugging code.
I have to get back to my assigned tasks, so I'll have to put this issue on hold for a while. The bug will go back into out backlog with some notes. I had hoped it would be easy to do, but it is not looking that way. I'll update this thread when I find some more time.
... View more
AdChoices