with crNoDrop cursor. On Linux gtk2 I see cursor is 2x-3x bigger than I seen it before, 2-3 months ago.

Alexey wrote

with crNoDrop cursor. On Linux gtk2 I see cursor is 2x-3x bigger than I seen it before, 2-3 months ago.

Maybe not related but this is my yesterday post to lazdevel list:

cursorimage.inc
TCursorImage.LoadFromResourceHandle()
Line 95

IconEntry.bWidth := DirEntry^.wWidth;
IconEntry.bHeight := DirEntry^.wHeight;

IconEntry members are byte, but DirEntry members are word, so range error occurs.

Note that range error does not occur with fpc-3.0.2 , but it happens with 3.0.4rc1.

So, maybe cast can fix your problem:
IconEntry.bWidth := Byte(DirEntry^.wWidth);
IconEntry.bHeight := Byte(DirEntry^.wHeight);

zeljko

Michl added high-resolution cursors recently. Obviously Gtk2 picks up the wrong size. Win32 works fine.

Ondrej

Ondrej Pokorny wrote

Michl added high-resolution cursors recently. Obviously Gtk2 picks up the wrong size. Win32 works fine.

This is a inconsistency between Linux and Windows. While on Windows the cursors are scaled after the DPI setting is changed, on Linux the cursors stays small. The cursors taken from the system are further small. The cursors taken from resourse are wrongly scaled.

Will see.

Michl

Michael W. Vogel wrote

This is a inconsistency between Linux and Windows. While on Windows the cursors are scaled after the DPI setting is changed, on Linux the cursors stays small. The cursors taken from the system are further small. The cursors taken from resourse are wrongly scaled.

Damn, I'm wrong. This was the behaviour after switching from 120 to 196DPI. Seems so, not all settings were correctly switched.

After a restart of that OS, revision 55794 works correct here (all cursors scaled, just crNo is to little, see test app on bugtracker): 64bit Linux Mint KDE 17.3 Lazarus 1.9.0 r55794 FPC 3.0.2 x86_64-linux-gtk2

Well, I think lets discuss it here:
https://bugs.freepascal.org/view.php?id=32385

Michl