#998 closed enhancement (wontfix)
cursors of any size on win32
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 2.4 |
Component: | platforms | Version: | 0.15.x |
Keywords: | win32 | Cc: |
Description (last modified by )
Split from #976, related to #734.
Links claiming we can only have fixed size (32x32 or 64x64 on high dpi displays):
- About Cursors
- CreateCursor: The nWidth and nHeight parameters must specify a width and height that are supported by the current display driver, because the system cannot create cursors of other sizes. To determine the width and height supported by the display driver, use the GetSystemMetrics? function, specifying the SM_CXCURSOR or SM_CYCURSOR value.
- The biggest size of Windows Cursor
- GetSystemMetrics function:
SM_CXCURSOR
: The width of a cursor, in pixels. The system cannot create cursors of other sizes.SM_CYCURSOR
: The height of a cursor, in pixels. The system cannot create cursors of other sizes.
That said, I also found: (dead link: https://support.microsoft.com/en-us/kb/307213
was Windows XP icon and cursor support) which states: The system also provides the SetSystemCursor API function that you can use to change the system cursor for specific categories. You can use this function to set a cursor of any size. However, you must call the function programmatically, and you can only use it to set a cursor for a specific category. You cannot use it to make all cursors on the system the same size.
Change History (4)
comment:4 Changed 4 years ago by
Description: | modified (diff) |
---|---|
Milestone: | 0.16 → 3.0 |
comment:5 Changed 3 years ago by
Milestone: | 3.0 → 2.4 |
---|---|
Status: | new → assigned |
comment:6 Changed 3 years ago by
Description: | modified (diff) |
---|---|
Resolution: | → wontfix |
Status: | assigned → closed |
comment:7 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/998
Note: See
TracTickets for help on using
tickets.
SetSystemCursor
changes are system-wide apparently, and those don't even work in windows 10.