Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GraphNode slots don't work if a non-Control node is added anywhere above the last child #91082

Closed
nagidev opened this issue Apr 23, 2024 · 0 comments · Fixed by #91083
Closed
Milestone

Comments

@nagidev
Copy link
Contributor

nagidev commented Apr 23, 2024

Tested versions

  • Reproducible in v4.3.dev.custom_build [c7f56d3], v4.2.2.stable.official [15073af]

System information

Godot v4.3.dev (c7f56d3) - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1650 (nvidia; 550.67) - Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz (8 Threads)

Issue description

Adding any node that is not a Control node as a child of a GraphNode and keeping it at an index that's not last, makes the slots at that index stop working. Dragging from those slots does not show a connection line.

Screenshot from 2024-04-24 02-18-31

Additionally, setting any non-last control node's size flag to expand makes the very last slot to stop working as well. However, this may be caused due to the slot drawing outside the GraphNode as noted in issue #85558

Steps to reproduce

  1. Create the following scene tree:
GraphEdit
└ GraphNode
  ├ Label
  ├ Timer
  └ Label2
  1. Set both the slots of the GraphNode to enabled (doesn't matter left or right).
  2. Run the scene and try to drag out both the slots.

Expected behaviour: both slot would show connection lines
Current behaviour: second slot does not show connection line

Note: Adding more non-Control nodes above the control nodes makes more slots stop working.

Minimal reproduction project (MRP)

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants