Snap Cursor to Selected (Edit Mode) : lack of control and hidden functionalities #52355
Labels
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#52355
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blender Version
Broken: all versions up to 2.79 RC2
Short description of error
In Edit Mode, when the pivot point is set to Median Point, the Snap Cursor to Selected operator uses the medians of the vertices. When the pivot point is set to Bounding Box Center, the cursor snaps to the bounding box. However, the confusing thing is that we would then expect this operator to be influenced by the Pivot Point setting (e.g. when set to Active Element it would snap to the active element), but that's not the case. Only Median Point has an influence on it. All the other settings result in snapping to the bounding box center. Of course there's the Snap Cursor to Active operator but then why not have a Cursor to Median operator ?
STEPS TO REPRODUCE
Open this file : Snap Cursor inconsistency.blend
be confused
And there's more.
When the Pivot point is set to Bounding Box, the pivot goes on the object-space bounding box, but the 3D cursor snaps to the world-space bounding box, not letting you any choice.
PROPOSAL
and make Median be the default when the Pivot Point is set to Median, World Bounds be the default when the Pivot is set to World Bounds, etc... so we have full control, no hidden functionality and no confusion.
Changed status to: 'Open'
Added subscriber: @ChameleonScales
This comment was removed by @ChameleonScales
This comment was removed by @ChameleonScales
Inconsistency in Snap Cursor operatorsto Inconsistency in Snap Cursor operators (Edit Mode)Added subscriber: @dfelinto
I can reproduce this. It seems more like a design issue than a(n implementation) bug.
Added subscriber: @zeauro
I agree it is a design discussion. But I don't see a real issue.
A user that doesn't know this behaviour will expect Snap Cursor to Selected to be restricted to one option.
But it is a plus to have choïce between Median of selected elements or Bounding Box Center of selection.
Option could be explicit. A checkbox option added to choose for this case would be sufficient to disconnect the operator from pivot point.
But it makes no sense to create a Cursor to Pivot Point operator. A confusion would be added by existence of pivot points that are making no sense for that action.
What would be the expected behaviour of a Snap Cursor to Cursor or a Snap Cursor to Individual Origins ?
And it is probably the reason why these irrelevant pivot points correspond to a default : Bounding Box Center.
They are making no sense for a snap cursor to selected operation and a solution is already provided for snap to active.
The object space bounding box for selection in edit mode can be seen as a user request.
It is probably something to add to brita's User Coordinate Spaces project.
https://developer.blender.org/T43964
You made some good points. I update my proposal :
Does this work for you ?
Yes. As is, it works. But, imho, it is a design task to archived as a todo.
It is weird to make such kind of changes at the end of a series.
There are probably other things that could benefit of an object space rather than global one.
Maybe your proposal would not stay relevant when this part of Blender would be reviewed by 2.8 project.
I haven't heard of a planned change in the behavior of the 3D cursor for 2.8 but I'm not involved enough to know. You probably know better, so, do as you wish
Inconsistency in Snap Cursor operators (Edit Mode)to Snap Cursor to Selected (Edit Mode) : lack of control and hidden functionalitiesAdded subscriber: @Sergey
Changed status from 'Open' to: 'Archived'
Thanks for the report, but it's simply how Blender works. Improvements are possible, but bug tracker is not the place to discuss such changes. Use bf-funboard mailing list for that and get someone to implement good proposal or submit a patch here :)