Interface - Large Cursors #73978

Closed
opened 2020-02-18 18:36:21 +01:00 by Josip Žukina · 22 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7
Worked: (optional)

Short description of error
The size and shape of the cursor doesn't change when you check "Large Cursor" box in the Interface - Display section of the Blender Preferences Window.

Exact steps for others to reproduce the error
First you need to be in Edit mode, then simply go to Edit - Preferences - Interface - Display - check and uncheck the box Large Cursors and you will see that the size and shape of the cursor doesn't change in the viewport
Based on the default startup.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `77d23b0bd7` Worked: (optional) **Short description of error** The size and shape of the cursor doesn't change when you check "Large Cursor" box in the Interface - Display section of the Blender Preferences Window. **Exact steps for others to reproduce the error** First you need to be in Edit mode, then simply go to Edit - Preferences - Interface - Display - check and uncheck the box Large Cursors and you will see that the size and shape of the cursor doesn't change in the viewport Based on the default startup.
Author

Added subscriber: @JoeZeph7

Added subscriber: @JoeZeph7
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member
Docs and hovering over it says "..when available" https://docs.blender.org/manual/en/latest/editors/preferences/interface.html?highlight=large%20cursors#display
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

The cursors don't change anymore based on the mode, but based on the selected tool. So don't expect the cursor to change by entering edit mode. The default OS cursors are not up-scaled at all, only our custom ones.

So if you select the Annotate tool for example, you should see a large pen cursor. Can you confirm that? Only if that doesn't work, we have a bug here.

The cursors don't change anymore based on the mode, but based on the selected tool. So don't expect the cursor to change by entering edit mode. The default OS cursors are not up-scaled at all, only our custom ones. So if you select the Annotate tool for example, you should see a large pen cursor. Can you confirm that? Only if that doesn't work, we have a bug here.
Member

Oh wait, I think OP is talking about "the cursor", the one that sits at the origin, by default.. but the pen cursor also didn't change, macOS here

Oh wait, I think OP is talking about "the cursor", the one that sits at the origin, by default.. but the pen cursor also didn't change, macOS here

Added subscriber: @jenkm

Added subscriber: @jenkm

It works in 2.80, for example, 'knife' cursor becomes large, but does not work in 2.83 (macOS).

It works in 2.80, for example, 'knife' cursor becomes large, but does not work in 2.83 (macOS).
Member

In #73978#875548, @jenkm wrote:
It works in 2.80, for example, 'knife' cursor becomes large, but does not work in 2.83 (macOS).

This is expected. The cursors were updated, but on macOS they don't respect the Large Cursors. Think that's because we'd have to provide the cursors with 4x the size then too (double pixel size due to Retina + Large Cursors), which would be nice to avoid due to binary size.

> In #73978#875548, @jenkm wrote: > It works in 2.80, for example, 'knife' cursor becomes large, but does not work in 2.83 (macOS). This is expected. The cursors were updated, but on macOS they don't respect the *Large Cursors*. Think that's because we'd have to provide the cursors with 4x the size then too (double pixel size due to Retina + *Large Cursors*), which would be nice to avoid due to binary size.

@JulianEisel on macOS cursors is .pdf (vector) so can be scaled, I guess.

@JulianEisel on macOS cursors is .pdf (vector) so can be scaled, I guess.

Added subscriber: @brecht

Added subscriber: @brecht

On macOS we use vector graphics for cursors, so it's not a size issue there.

Really the Large Cursors setting is intended to be removed. We should be following the operating system settings for cursor size, and all cursors should be readable at that size. I haven't checked how close we are to that after the cursor changes in 2.81.

On macOS we use vector graphics for cursors, so it's not a size issue there. Really the Large Cursors setting is intended to be removed. We should be following the operating system settings for cursor size, and all cursors should be readable at that size. I haven't checked how close we are to that after the cursor changes in 2.81.
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

On Windows it is possible for us to make the changes necessary to make these new cursors (like Knife) obey the "Large Cursors" option in Preferences. In fact that was a part of my original proposed patch when we did the updated.

However we decided to leave that part out of it. For one it was not possible to do on Mac. And even on Windows it was only possible to force our custom cursors large, but the default "pointer" cursor would still stay the same size. The only way I found to get around this was to include our own version of the "pointer" cursor in our binary. But that was considered a bit silly. And we really wouldn't want to duplicate all the OS-supplied cursors in that way.

At the moment the real "bug" is probably that we have that "large cursors" checkbox at all. AFAIK it would only have visible change on Linux and that would just be for our custom cursors with the rest of them still remaining the same size. I think we should remove the "Large Cursors" option.

On Windows it is *possible* for us to make the changes necessary to make these new cursors (like Knife) obey the "Large Cursors" option in Preferences. In fact that was a part of my original proposed patch when we did the updated. However we decided to leave that part out of it. For one it was not possible to do on Mac. And even on Windows it was only possible to force our custom cursors large, but the default "pointer" cursor would still stay the same size. The only way I found to get around this was to include our own version of the "pointer" cursor in our binary. But that was considered a bit silly. And we really wouldn't want to duplicate all the OS-supplied cursors in that way. At the moment the real "bug" is probably that we have that "large cursors" checkbox at all. AFAIK it would only have visible change on Linux and that would just be for our custom cursors with the rest of them still remaining the same size. I think we should remove the "Large Cursors" option.

We should be following the operating system settings for cursor size, and all cursors should be readable at that size.

Yes it works for Mac.

cursor.png

> We should be following the operating system settings for cursor size, and all cursors should be readable at that size. Yes it works for Mac. ![cursor.png](https://archive.blender.org/developer/F8348551/cursor.png)

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

I think we could just remove Large Cursors. You can set this in the OS anyway if you need it for Accessibility reasons.

I think we could just remove Large Cursors. You can set this in the OS anyway if you need it for Accessibility reasons.
Member

#63726 should it be a todo ?

#63726 should it be a todo ?

This issue was referenced by 85f980c517

This issue was referenced by 85f980c517e42d41352bf7190ae850239edc2f88
Member

Changed status from 'Needs User Info' to: 'Resolved'

Changed status from 'Needs User Info' to: 'Resolved'
Ankit Meel self-assigned this 2020-02-28 21:28:55 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#73978
No description provided.