You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest that when the user selects the 'mouse pointer crosshair' functionality and the mouse pointer is moved to a high resolution screen, that the crosshair strokes are thickened by a parameterized value. For example, it could go from 2 pixels to 4 pixels. With this, the mouse pointer would be visible more easily on high-resolution monitors.
I use this feature because I have two 1080p monitors and one 4K monitor on my computer and it is very difficult to locate the mouse pointer when I move it to the 4K monitor.
Scenario when this would be used?
It would be very useful for users with monitors with different resolutions, helping to quickly locate the mouse pointer.
Supporting information
No response
The text was updated successfully, but these errors were encountered:
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Description of the new feature / enhancement
I would like to suggest that when the user selects the 'mouse pointer crosshair' functionality and the mouse pointer is moved to a high resolution screen, that the crosshair strokes are thickened by a parameterized value. For example, it could go from 2 pixels to 4 pixels. With this, the mouse pointer would be visible more easily on high-resolution monitors.
I use this feature because I have two 1080p monitors and one 4K monitor on my computer and it is very difficult to locate the mouse pointer when I move it to the 4K monitor.
Scenario when this would be used?
It would be very useful for users with monitors with different resolutions, helping to quickly locate the mouse pointer.
Supporting information
No response
The text was updated successfully, but these errors were encountered: