opened
CryZe
username_0
The Splits Editor should act similar to a component. So pretty much everything about it should be implemented in livesplit-core. The Splits Editor provides a state object that contains all the necessary information for visualizing it in any kind of UI.

Things to clear up: Should the Splits Editor directly modify the Run object that is in use by the timer and keep a clone in case we need to cancel our progress, or should we just modify the clone in the first place and replace the Run used by the timer once the changes are approved. The former case has a lot of issues with potential race conditions and forces us to introduces reference counting and reader writer locks in most of the code we already wrote. However it models what the original LiveSplit is doing more closely.
Implement the Splits Editor
issue
created
CryZe
username_0
Currently sketching out the whole thing without writing any actually UI for it, to reduce the scope of the whole situation. Also for the same reason I'm not bothering with any kind of live-editing for now. It shouldn't be all too hard switching to live-editing later.
comment
closed
CryZe
username_0
issue