Nominal size vs. actual image size about hyprcursor HOT 5 CLOSED

https://invent.kde.org/plasma/breeze/-/blob/master/cursors/Breeze/Breeze/cursors/bottom_right_corner is an example with hotspot at the bottom right corner in the 32x32 pixmap, with a nominal size of 24.

from hyprcursor.

SVGs have no size - all SVG cursors are required a size of 0 (in >0.1.5 they are forced to be 0 anyways)

PNGs should be exactly the size they advertise - true. I can add that to docs and enforce in lib.

I don't see a point in having two sizes (nominal and actual)

from hyprcursor.

That would be fine. Some conversion from XCursor might fail, but I don't think many people will do the conversion just to save space, anyway. SVG is the point.

The other direction - generate a XCursor theme from a hyprcursor theme, seems more useful, as I can deploy a small hyprcursor package to the end user, and in its postinstall script, generate a XCursor theme for compatibility.

from hyprcursor.

it's in the todo but I put off doing it as all themes so far have come from x anyways.

from hyprcursor.

I think I know why Breeze cursors are set in that way:

Left: Adwaita, Right: Breeze, in the same nominal size.

You can see that the main "arrow" part of the Breeze cursor is roughly the same size as the Adwaita one, only the "badge" is outside the nominal size bounds.

So if we set the nominal size of Breeze to the actual 32px instead of the current 24px, the end user would feel that it's "smaller" than Adwaita at the same 32px nominal size.

Anyway, I'll try to set the Breeze nominal size to the actual size. Seems more straightforward this way.

from hyprcursor.