Comment 117 for bug 151448

A little more testing with DEBUGLEVEL=+msg,+win and sai.exe showed that the window registered to the tablet events differed from the window that was receiving mouse click events from clicking down with my stylus. Also, I couldn't figure out how to get a log of *all* input events (hoping to see Wine recognize that packets of some kind were coming from my tablet, somewhere), and the only events I could catch with +msg were those of normal mouse clicks from the pen. I thought it was odd that they were treated only as normal mouse clicks.

Maybe there's some kind of regression in finding the correct window. Many earlier patches in the thread dealt with this. Krita had a similar problem but I didn't thoroughly investigate it in the same way (it may also be useful to check easily accessible wintab-using programs like Gimp

My volatile testing environment ate my latest logs for this, but if you need any more than the ones in my last comment, I can re-create them.