http://bugs.winehq.org/show_bug.cgi?id=44887 woofinmuffin <wfnmuffin@proton.me> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wfnmuffin@proton.me --- Comment #8 from woofinmuffin <wfnmuffin@proton.me> --- This bug is caused by wSerial being incremented by ZBrush internally while file selector is open, while wintab32.dll does not. This causes desynchronization of wSerial numbers between both, and makes ZBrush request WTPacket that have higher wSerial than anything in wintab32's PacketQueue. Both will keep increasing this after popup closes, and it will never match anything in queue after that. I was able to make a bypass for this issue, by making the WTPacket check if ZBrush asks for higher wSerial twice, and if so, just set that serial to whatever ZBrush requests on last available packet in PacketQueue. This makes wintab32.dll resynchronize with ZBrush internal wSerial index, and makes the pen pressure just work after any interaction with any popup. I'm not sure if this is a quirky implementation of wintab in ZBrush, or wine not keeping track of pen events when, the main window that created wintab context, is blocked by a file selector window (that freezes main window both running native on windows and in wine, plus afaik doesn't use wintab at all). I cannot contribute quality code for this project, sorry. I'm including modified context.c from wine-10.20 as a reference. (only BOOL WINAPI WTPacket function is changed) I would also add TRACE() if executable asks for invalid wSerial for any similar cases. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.