Node Editor: Some nodes lack red line when muted #58508
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#58508
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?
Node Editor: Some nodes lack red line when muted
System Information
System: Windows 7 64bit
RAM: 4096 MB
renderer: 'GeForce GTX 760/PCIe/SSE2'
vendor: 'NVIDIA Corporation'
version: '4.5.0 NVIDIA 364.72'
Blender Version
Broken: blender-2.80.0-git.0f5b53ba4dc-windows64
Short description of error
Node Editor: Some nodes lack red line when muted
Exact steps for others to reproduce the error
Expected:
I didn't find any indication in the properties either,
and the changed colors of the node header don't tell anything
Added subscriber: @MichaelParucha
Added subscribers: @WilliamReynish, @brecht, @JacquesLucke
The red line indicates which input will be passed on at which output when the node is muted. On some nodes that does not make any sense. E.g. passing on the vector as color in the gradient texture node makes no sense.
Nevertheless I agree that some other indication is necessary here (or it should just not be possible to mute those nodes!).
@brecht, @WilliamReynish what do you think?
I think it's best to be consistent. Even if there's only one input and one output, we could still display the red line. The line both helps communicate what happens when a node is disabled, and the fact that it is disabled at all.
I see no immediate downside to just always drawing the red line when disabled. You then also know which socket to use when connecting to a disabled node.
We could also make the node header properly red and grey out all the buttons in the node.
If we want to draw the red line, I guess it would have to be connected to some arbitrary point on the left side of the node. Some disabled nodes don't even have input sockets.
Mainly I think the regression compared to 2.7x is the theming, which does not make the header red enough. This should at least be fixed.
Hm, true. Probably better then to just grey out the contents of the node.
The line I see we can't always use, and the theme thing will never be clear enough I don't think.
Closed as duplicate of #60719