Closed boatbomber closed 1 month ago
not much we can do about it, but I'm still unhappy
Sums up a lot of Rojo work, doesn't it ðŸ˜
Does the problem in the linked issue only occur for changed class names? We destroy instances for normal removals, too
Good catch, Ken. Updated all uses of Destroy
to be Parent = nil
, and updated all the relevant tests to pin this behavior.
Adopts the latest ChangeHistoryService APIs. Our Undo/Redo notification warnings (to prevent accidentally undoing a Rojo patch) still work fine with this new API.
Avoids the permanent Destroy action, uses Remove instead. This closes #914.