Moving sockets in custom nodes not working #119464

New Issue

Diego Gangl · 2024-03-14T15:02:55+01:00

Diego Gangl commented

2024-03-14 15:02:55 +01:00

System Information
Operating system: Linux 6.7.4 (Fedora 39)
Graphics card: AMD VEGA 64

Blender Version
Broken: 4.0.2 (9be62e85b7)
Worked: Blender 3.3 LTS

Short description of error

Calling move() on the inputs of a custom socket doesn't move the sockets. Currently it seems to move some sort of separator but only on certain indexes, for most it doesn't do anything.

Exact steps for others to reproduce the error

Open the attached Blend file
Run the top script so the custom node gets registered
Run the lower script to check what the move function does

Alternatively, use the console to call move() with other indexes.

**System Information** Operating system: Linux 6.7.4 (Fedora 39) Graphics card: AMD VEGA 64 **Blender Version** Broken: 4.0.2 (9be62e85b727) Worked: Blender 3.3 LTS **Short description of error** Calling `move()` on the inputs of a custom socket doesn't move the sockets. Currently it seems to move some sort of separator but only on certain indexes, for most it doesn't do anything. **Exact steps for others to reproduce the error** 1. Open the attached Blend file 2. Run the top script so the custom node gets registered 3. Run the lower script to check what the move function does Alternatively, use the console to call `move()` with other indexes.

test_move_bug.blend

934 KiB

Diego Gangl added the

labels 2024-03-14 15:02:55 +01:00

Germano Cavalcante commented

2024-03-14 19:02:04 +01:00

I can confirm that the behavior has changed.

Apparently, the script appears to update the node type.
It does not update existing nodes that have the same type.
Only if you add another one.

Note: there appears to be an error in usage.
The informed node has 3 inputs whose indexes are 0, 1, 2.
It does not have an input with index 3.

Cc. @JacquesLucke

I can confirm that the behavior has changed. Apparently, the script appears to update the node type. It does not update existing nodes that have the same type. Only if you add another one. ![image](/attachments/b190fc28-2c80-410c-a9b2-30012c2e798d) Note: there appears to be an error in usage. The informed node has 3 inputs whose indexes are 0, 1, 2. It does not have an input with index 3. Cc. @JacquesLucke

image.png

21 KiB

Germano Cavalcante added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Moving sockets in custom nodes not working #119464