https://bugs.winehq.org/show_bug.cgi?id=47386
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d
--- Comment #2 from Zebediah Figura z.figura12@gmail.com --- The application creates a 64x64 texture and sets it as the cursor using IDirect3DDevice9::SetCursorProperties(). This results in wined3d creating a "software" cursor. It never updates the cursor position, and wined3d never does of its own volition, so the cursor never moves on the screen.
I tested on a native Windows machine. Setting a 64x64 cursor using SetCursor() succeeds, and switching the texture size to 64x64 in test_cursor() in d3d9:device has no effect on the test (i.e. GetCursorInfo() does not report that the cursor has been replaced). So that's interesting. Either native d3d9 is using a "hardware" cursor in that case (despite the documentation), or its "software" cursor involves updating the cursor position (somehow). I'm not sure how to test this, however, since I'm unable to get SetCursor() to refuse anything on native Windows.