Hi,
Does this address Alexandre's need for a software cursor, or is this unrelated?
In the tests I recommend to test a bigger cursor in addition to the 32x32 cursor to see what happens in situations where Windows falls back to a software cursor.
Stefan
On Thursday 20 October 2011 12:42:55 Henri Verbeet wrote:
dlls/wined3d/device.c | 8 +++++++- 1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/dlls/wined3d/device.c b/dlls/wined3d/device.c index 67e50b5..6f43715 100644 --- a/dlls/wined3d/device.c +++ b/dlls/wined3d/device.c @@ -5251,10 +5251,16 @@ void CDECL wined3d_device_set_cursor_position(struct wined3d_device *device, device->xScreenSpace = x_screen_space; device->yScreenSpace = y_screen_space;
- /* switch to the software cursor if position diverges from the
hardware one */ if (device->hardwareCursor) { POINT pt;
GetCursorPos( &pt );
if (x_screen_space == pt.x && y_screen_space == pt.y)
return;
SetCursorPos( x_screen_space, y_screen_space );
/* Switch to the software cursor if position diverges from the
hardware one. */ GetCursorPos( &pt ); if (x_screen_space != pt.x || y_screen_space != pt.y) {
On 21 October 2011 17:12, Stefan Dösinger stefandoesinger@gmx.at wrote:
Does this address Alexandre's need for a software cursor, or is this unrelated?
It's related, but software cursors are still somewhat broken.