Mac OS X 10.11.4: With the “Cursor size” set to Large in Accessibilty, custom cursors are limited to 2x resolution
| Originator: | |||
| Number: | rdar://25641415 | Date Originated: | 09-Apr-2016 02:54 PM |
| Status: | Open | Resolved: | |
| Product: | OS X SDK | Product Version: | Mac OS X 10.11.4 (15E65) |
| Classification: | UI/Usability | Reproducible: | Always |
Summary: When increasing the “Cursor size” to Large (4x default resolution) in the Vision > Display section of the Accessibility system preferences, custom cursors are limited to the 2x resolution representation scaled up, while system-provided cursors are displayed at full resolution. The custom cursor is created in the way described here: http://stackoverflow.com/questions/19245387/nscursor-using-high-resolution-cursors-with-cursor-zoom-or-retina This method provides custom cursors for scale factors, 1 thru 4. This can easily be increased to 8 for Large cursors for retina 2x resolution. Steps to Reproduce: 1. Build and run an OS X app that displays custom cursors and 2. Set the “Cursor size” to Large in the Vision > Display section of the Accessibility system preferences 3. Switch to custom cursors app & view and observe the scaled-up/pixelated cursor 4. Move the cursor outside of the custom cursor view or window and observe that the system-provided cursor is perfectly resolved Expected Results: The appropriate cursor image representation should be used instead of a lower resolution one used scaled up. Actual Results: The 2x resolution representation is scaled up to fill the cursor frame. Regression: none Notes: It would be even better, if a resolution independent cursor image could be provided to NSCursor’s -initWithImage:hotSpot: so that it can do “the right thing” to get smooth, sharp cursors under all possible circumstances.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!