Nodes: Copy-pasting nodes makes many active nodes #108049
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#108049
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: Current main.
Worked: Never.
Short description of error
Move nodes.
Copy nodes.
Change property on multiple node synchrony.
...
It node properties displaed in N-panel:
It node renamed by opertor:
...
This report combine some other reports:
Exact steps for others to reproduce the error
Ctrl+C,Ctrl+V.A.Look at many active nodes, instead of one active (new one) and old one selected only.
Same in python api:
bpy.data.node_groups[0].nodes.activ(it display jast only first active one).Same in property panel.
Npdes: Activity is ignored, selection used as active state of nodeto Nodes: Activity is ignored, selection used as active state of nodeI think #108036 described pretty well a scenario that could be considered a bug.
But what is the actual bug in this report?
Discussions about
activevs.selectedhave been around for ages, see #82359 for example, dont think we have to open another report for this discussion?Rechecking everything now... seems like I misunderstood the bug.
I will describe it like this: duplication of nodes can lead to a situation where you have several active nodes:
Initially, I mistook this for the fact that the selection in the principle is incorrect.
I decided to combine all the reports related to this, so that it would be easier to describe the problem. Normally I would just edit one original
Again: #108036 described this pretty well (had reproduction steps etc.)
Regarding this report:
How do you get to the state of your screenshot?
I cant seem to repro, I only ever get one node with a white outline...
I did not set out to describe the steps here, sorry. I initially followed the behavior trail (selection is always considered an activity (which turned out to be just a consequence of duplication)).
And in this context, I saw it as: hey, we have a strange behavior that seems to be noticed by everyone. If no one minds, I'll fix it.
But seeing now that I was on the wrong track, it might make sense to change the report a bit.
Nodes: Activity is ignored, selection used as active state of nodeto Nodes: Duplicating nodes makes many active nodesThere is technically never gonna be multiple "active" nodes, the "multiple actives" is tagged on the node but theres another "active" inside space data. maybe both are needed, but obviously they need to be in sync
Just to be clear:
Ctrl C Ctrl Vcopy-paste (seeing multiple active nodes there)Shift D(only ever get one active node then)@ChengduLittleA , @mod_moder : are you really getting this for Shift D as well?
Philipp Oeser referenced this issue2023-06-02 11:25:14 +02:00
That's right, the second can be removed from the description
@lichtwerk Nope only ctrl c/v has this problem.
Nodes: Duplicating nodes makes many active nodesto Nodes: Copy-pasting nodes makes many active nodes