A bunch of parts of QuickAtlas are implemented twice. Once for "normal" responding to interactions from the user, and a second time for Do/Undo function calls.
Consolidating the interactions into the Do/Undo functions should simplify the flow of QuickAtlas and reduce the chance of having stuff work in normal interaction and break when Undo/Redo happens.
A bunch of parts of QuickAtlas are implemented twice. Once for "normal" responding to interactions from the user, and a second time for Do/Undo function calls.
Consolidating the interactions into the Do/Undo functions should simplify the flow of QuickAtlas and reduce the chance of having stuff work in normal interaction and break when Undo/Redo happens.