I have a custom method to create (and automatically link) nodes in a chain. Each ‘link’ in the chain is its own document transaction. Each transaction contains both a JGoBasicNode creation and a JGoLink creation, except the caboose link in the chain, which obviously contains just a node.
When I undo, it undoes each link in the chain individually, as expected. When I redo, it puts them back. However, after being redone, the front end of each JGoLink is no longer connected to the BasicNode in front of it - when I attempt to move the BasicNode, it disconnects.
If I move the node that the tail of the link is connected to, and the connection was never severed via undo/redo, it snaps back onto the link it was broken from. Then if I move the head node, it breaks again.
I don’t understand why the link can think it’s connected to both ports (head and tail) correctly when you move a node whose creation was not undone/redone, but when you move a node whose creation was undone/redone, it no longer thinks it’s connected to the tail only.
Do you guys know what I’m missing? I’m hoping that it is something you have seen before with a quick answer. I’ll describe the way I’m creating the transactions if you’ve never seen this symptom before.