Snapping in the shader editor is linked with the 3d View. #82713

Closed
opened 2020-11-14 06:18:04 +01:00 by CobraA · 7 comments

System Information
Operating system: Windows 10 64 Bits
Graphics card: GTX 1080 Ti

Blender Version
Broken: version: 2.91.0 bee5921e82

Short description of error
When I enable snapping in the shader editor it gets enabled in the 3d viewport, this is somehow confusing.
Shouldn't each editor control it's own snapping option?
{F9281156 size = full}
Exact steps for others to reproduce the error

  • Open shader Editor.
  • Enable Snapping option or Shift+tab.
  • In the 3d Viewport you'll see the snapping option also enabled.
**System Information** Operating system: Windows 10 64 Bits Graphics card: GTX 1080 Ti **Blender Version** Broken: version: 2.91.0 bee5921e82eb **Short description of error** When I enable snapping in the shader editor it gets enabled in the 3d viewport, this is somehow confusing. Shouldn't each editor control it's own snapping option? {[F9281156](https://archive.blender.org/developer/F9281156/snap.gif) size = full} **Exact steps for others to reproduce the error** * Open shader Editor. * Enable Snapping option or Shift+tab. * In the 3d Viewport you'll see the snapping option also enabled.
Author

Added subscriber: @CobraA

Added subscriber: @CobraA

Added subscriber: @rjg

Added subscriber: @rjg

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Robert Guetzkow self-assigned this 2020-11-14 10:16:23 +01:00

Thank you for your report. The use_snap is part of the bpy.types.ToolSettings. These settings apply to the entire scene, e.g for the current scene the use_snap property can be accessed through bpy.context.scene.tool_settings. This is not a bug, but a design choice.

Thank you for your report. The [use_snap ](https://docs.blender.org/api/current/bpy.types.ToolSettings.html#bpy.types.ToolSettings.use_sna) is part of the `bpy.types.ToolSettings`. These settings apply to the entire scene, e.g for the current scene the `use_snap` property can be accessed through `bpy.context.scene.tool_settings`. This is not a bug, but a design choice.
Author

In #82713#1054728, @rjg wrote:
Thank you for your report. The use_snap is part of the bpy.types.ToolSettings. These settings apply to the entire scene, e.g for the current scene the use_snap property can be accessed through bpy.context.scene.tool_settings. This is not a bug, but a design choice.

Okay then, it's going to be a feature request, because from a user point of view it doesn't make any sense.

> In #82713#1054728, @rjg wrote: > Thank you for your report. The [use_snap ](https://docs.blender.org/api/current/bpy.types.ToolSettings.html#bpy.types.ToolSettings.use_sna) is part of the `bpy.types.ToolSettings`. These settings apply to the entire scene, e.g for the current scene the `use_snap` property can be accessed through `bpy.context.scene.tool_settings`. This is not a bug, but a design choice. Okay then, it's going to be a feature request, because from a user point of view it doesn't make any sense.

Feature requests are off-topic on the bug tracker. Please use one of our channels listed on the following website for your proposal: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

Feature requests are off-topic on the bug tracker. Please use one of our channels listed on the following website for your proposal: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
Author

In #82713#1054893, @rjg wrote:
Feature requests are off-topic on the bug tracker. Please use one of our channels listed on the following website for your proposal: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

Yeah. I know that but sometimes usability issues and feature requests get mixed and this is one of them, anyway i made a request on RCS to change it.

> In #82713#1054893, @rjg wrote: > Feature requests are off-topic on the bug tracker. Please use one of our channels listed on the following website for your proposal: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests Yeah. I know that but sometimes usability issues and feature requests get mixed and this is one of them, anyway i made a request on RCS to change it.
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
2 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#82713
No description provided.