|User Action||nodecollectionchange cause||nodecollectionchange changeType||historychange cause||What to do?|
|Drop new node||drop||insert||undefined||Add new node to database|
|Undo drop||unknown||remove||undo||Remove node from database|
|Redo drop||historychange||insert||redo||Add node to db with previous properties|
|Delete the node||unknown||remove||undefined||Remove node from database|
|Undo delete||historychange||insert||undo||Add node to db with previous properties|
|Redo delete||unknown||remove||redo||Remove node from database|
Thanks for the tip.
It seems that if the nodecollectionchange changeType is remove, I cannot rely on the nodecollectionchange cause to determine if an undo or redo was just performed.
Instead I'm setting a global variable in the historychange event to indicate this action.
Is this correct? Should the nodecollectionchange cause not be "historychange" if I do a redo?
This post will be permanently deleted. Are you sure you want to continue?
Sorry, An error occured while processing your request. Please try again later.