07-03-2019, 11:21 AM
Hey Tyson,
Very minor bug, easy to replicate and work around but I figured you'd want to squash it.
Create a new Tyflow and add any birth operator.
Create a new, independent operator, either drag from the depot or tab->create, both methods work and every operator I tried showed the issue.
With the title bar of the new event node selected/highlighted, drag the new operator into the birth event node.
Delete the remaining isolated node, and the newly added operator should also be deleted, as though it's still part of it's original node.
This only appears to happen on the initial move of the operator to the birth node; once it's title bar has been deselected the connection is broken, and re-selecting it again before deleting the redundant node behaves as you would expect.
Running max 2018 & tyflow_016035
Very minor bug, easy to replicate and work around but I figured you'd want to squash it.
Create a new Tyflow and add any birth operator.
Create a new, independent operator, either drag from the depot or tab->create, both methods work and every operator I tried showed the issue.
With the title bar of the new event node selected/highlighted, drag the new operator into the birth event node.
Delete the remaining isolated node, and the newly added operator should also be deleted, as though it's still part of it's original node.
This only appears to happen on the initial move of the operator to the birth node; once it's title bar has been deselected the connection is broken, and re-selecting it again before deleting the redundant node behaves as you would expect.
Running max 2018 & tyflow_016035
Both the operator and the event are deleted in your case, because they're both still selected. However, even though the logic is technically sound, I can appreciate that for convenience sake to the user, it probably makes sense to deselect any currently-selected events after dragging operators around. I can't think of a case where you'd want to retain selection on an event after drag/dropping an operator inside of it. I'll see about fixing that up for the next version.