https://bugs.winehq.org/show_bug.cgi?id=47386 --- Comment #7 from Zebediah Figura <z.figura12(a)gmail.com> --- With <https://source.winehq.org/patches/data/167302> this is improved; i.e. the cursor actually moves. However, it flickers badly for me. I think this is because the applications is repeatedly (once per WM_SETCURSOR message? I didn't check) calling SetCursorProperties() with the same properties, and we destroy and recreate the cursor each time. I think the right thing to do is to check if the cursor texture and hotspot are the same, and skip setting it if so, but wined3d_device_set_cursor_properties() contains a warning not to hold a reference to the cursor texture, for fear of creating a circular reference. That warning dates back to 2006 (65e5ed60ae02), though, so I'm not sure if it's still salient. D3D refcounting is not exactly trivial... -- 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.