Shader editor: nodes moved with G key added to frames based on cursor position #80218

New Issue

Bernhard Engstler · 2020-08-29T13:58:16+02:00

Bernhard Engstler commented

2020-08-29 13:58:16 +02:00

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: c113af8288 (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

**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: `c113af8288` (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

Bernhard Engstler commented

2020-08-29 13:58:16 +02:00

Added subscriber: @B_Engstler

Germano Cavalcante commented

2020-09-01 16:09:59 +02:00

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

Sebastien Larocque commented

2021-04-20 15:13:05 +02:00

Added subscriber: @SebBlender

Sebastien Larocque commented

2021-04-22 18:08:07 +02:00

I had the same problem. I wanted to report this issue and I found this thread. I can see the issue has been reported many ago, but has not been addressed yet. I have a suggestion for the time when it is going to be fixed.

It would be interesting to have a visual cue indicating when the nodes are going to be included in the frame. It’s the same concept as the button highlight when doing a mouse over a button with the cursor. The highlight indicates what actions are possible. It’s something standard in terms of UI design and it would help to be more precise with the drag & drop of the nodes in frames. I find this especially more important since moving nodes to a frame is less precise than moving a simple icon because the nodes often form groups with complex shapes. The groups of nodes can even overlap several frames when being dragged.

I had the same problem. I wanted to report this issue and I found this thread. I can see the issue has been reported many ago, but has not been addressed yet. I have a suggestion for the time when it is going to be fixed. It would be interesting to have a visual cue indicating when the nodes are going to be included in the frame. It’s the same concept as the button highlight when doing a mouse over a button with the cursor. The highlight indicates what actions are possible. It’s something standard in terms of UI design and it would help to be more precise with the drag & drop of the nodes in frames. I find this especially more important since moving nodes to a frame is less precise than moving a simple icon because the nodes often form groups with complex shapes. The groups of nodes can even overlap several frames when being dragged.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Shader editor: nodes moved with G key added to frames based on cursor position #80218