http://bugs.winehq.org/show_bug.cgi?id=11846
--- Comment #46 from billstei billstei@hbci.com 2008-11-01 14:55:34 --- Regarding differences between ArtWeaver (working) and Sai (not working) with comment #43 setup, both wintab32 traces typically begin with a "motion_event" and end with a "WTPacket Returning 1", however in the case of ArtWeaver these additional calls are made after WTPacket Returning 1 and before the next motion_event (typical example shown):
trace:wintab32:WTInfoT (100, 15, 0x32fd10, 0) trace:wintab32:X11DRV_WTInfoW (100, 15, 0x32fd10) trace:wintab32:WTInfoT returns 16 trace:wintab32:WTInfoT (100, 15, 0x32fd00, 0) trace:wintab32:X11DRV_WTInfoW (100, 15, 0x32fd00) trace:wintab32:WTInfoT returns 16