Joel Graff
After digging through several issues (one of which involved a missing path variable), the fault I'm encountering lies with the launch() function in comm.R. Specifically, ``` launch
Explore creating a geometry tracker to abstract geometry specific tracker features to rebase node / wire / curve trackers on (update(), points, etc).
Tracker event order needs to be canonized for clarity. Currently task->alignment->node->wire->curve...?
Curve tracker code leaves much to be desired with too much state being maintained / exceptions, etc. Poss. migrate some functionality into base / node / wire trackers or state...
Make BaseDraggableTracker vs BaseTracker
Add spiral curve support for drag operations
Replace use of dictionaries throughout project with python data container object classes in the project/containers module.
If XML data doesn't correpond with calculated values, notify user and chooose default course of action. Preserve coordiantes where possible, but with spirals this may be superfluous