Skip to content

[bug]: node connection duplicated if droped in specific location. #7127

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

Closed
1 task done
skunkworxdark opened this issue Oct 16, 2024 · 2 comments · Fixed by #7791
Closed
1 task done

[bug]: node connection duplicated if droped in specific location. #7127

skunkworxdark opened this issue Oct 16, 2024 · 2 comments · Fixed by #7791
Labels
bug Something isn't working

Comments

@skunkworxdark
Copy link
Contributor

Is there an existing issue for this problem?

  • I have searched the existing issues

Operating system

Windows

GPU vendor

Nvidia (CUDA)

GPU model

4090

GPU VRAM

24GB

Version number

5.2.2rc2

Browser

chrome

Python dependencies

No response

What happened

First reported here in discord https://discord.com/channels/1020123559063990373/1149506274971631688/1294630773818921052

There is an issue in the nodes editor. This is a pain if you are replacing a node that doesn't auto-update (e.g. flux denoise) properly and you want to drag the noodle one at a time from the old one to the new one you can get duplicated connections.

Recording.2024-10-12.125429.mp4

After fiddling a little more with this I am fairly sure it's related to dropping the noodle on both a connector and on the node where it tries to add it automatically to the right connector at the same time.

Recording.2024-10-12.131302.mp4

What you expected to happen

Not to duplicate noodle connections

How to reproduce the problem

See videos

Additional context

No response

Discord username

skunkworxdark

@skunkworxdark skunkworxdark added the bug Something isn't working label Oct 16, 2024
@skunkworxdark
Copy link
Contributor Author

@psychedelicious This is still an issue in 5.8

its particularly annoying if you are replacing a node with a lot of connections with the same types.

@psychedelicious
Copy link
Collaborator

Thanks for the ping, I missed this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants