Page MenuHome

Shader editor: nodes moved with G key added to frames based on cursor position
Confirmed, NormalPublicBUG

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06

Blender Version
Broken: version: 2.83.4, branch: master, commit date: 2020-08-05 06:00, hash: rBc113af82881a (also with the 2.90 beta from August 25th)
Worked: I don't know. I remember this strange behaviour for a long time (2.80?) but could not pinpont the exact behaviour until now

Short description of error
In shader editor, when you have a frame and move nodes outside it with the shortcut G, the node is added to the frame based on the cursor position and not on the node position.
As expected, when pressing G key, a user does not align the cursor to the node to be moved but presses the G key regardless of the cursor position.

Exact steps for others to reproduce the error
-Default startup file
-In shader editor, add and join some nodes into a frame (Ctrl J)
-Grab another node outside the frame with G with the cursor position far from the node to be moved
-Move the cursor so that the cursor is inside the frame but the node is not and click to confirm new position
-The node is added to the frame based on the cursor position although it is far outside the frame

Event Timeline

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.Tue, Sep 1, 4:09 PM
Germano Cavalcante (mano-wii) updated the task description. (Show Details)
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".