You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you install Natron using the official installer?
Yes, I used the official installer
No, I installed from a binary archive
No, I compiled Natron from sources
No, I installed Natron via another method
Custom installation path
No response
What were you trying to do?
Undo a mistaken duplicate node connection (node A connected twice to node B via two connections)
What did you expect to happen? What happened instead?
Instead of disconnecting the last connected input (i.e. Mask) and keeping the original connection (i.e. input A), it disconnected input A and left the Mask input connected.
Here's a video demonstrating the issue:
2022-10-16.11-52-16.mp4
Step-by-step reproduction instructions
Start Natron
Add any node (Constant should work)
Add a Merge node
Connect Merge's A input into the first node
Connect Merge's Mask input into the same node
Undo.
Additional details
No response
The text was updated successfully, but these errors were encountered:
Make sure to follow our issue report guidelines
Natron version
Natron version 2.4.3 Release
Operating system
Windows 10 Pro [1909]
System specs
RAM: 32GB
CPU: AMD Ryzen 7 3700x
GPU: NVidia RTX 3060
Did you install Natron using the official installer?
Custom installation path
No response
What were you trying to do?
Undo a mistaken duplicate node connection (node A connected twice to node B via two connections)
What did you expect to happen? What happened instead?
Instead of disconnecting the last connected input (i.e. Mask) and keeping the original connection (i.e. input A), it disconnected input A and left the Mask input connected.
Here's a video demonstrating the issue:
2022-10-16.11-52-16.mp4
Step-by-step reproduction instructions
Constant
should work)Merge
nodeMerge
's A input into the first nodeMerge
's Mask input into the same nodeAdditional details
No response
The text was updated successfully, but these errors were encountered: