Potential improvement #2
Description
Hi, while this tool certainly is very useful in its current state, I have a few potential ideas for improvement. Currently, it seems to only be useful for first-runs and for examining past runs (add a new split to the end and start timer and you can see the exact splits -- I can now see what my new PB looks like compared to my old PB which I couldnt in the past).
What I am proposing here would fix the first issue, maybe. What if instead of looking at the last timed split, you look at the name of the split instead? Basically, what my idea is, say:
You have three splits:
A
B
C
When you start the timer, the name of the first split would change
A(*)
B
C
And when you split, it would change the names of the first and second split:
A
B(*)
C
Basically, keep track of which split is being used. You can then pause and reset, and continue at a later point. And of course, when you finish the run, the last (*) will be cleared out, ready to start a new run. This would have the benefit of being able to start at any point of a speedrun (not being limited to the last timed split), therefore being able to compare directly to your PB instead of having to empty your splits and have a second component.
I would do this myself if I was better at coding than I currently am, lol
I also noticed it completely warps the average/median times, but so far I have not managed to think up a solution besides creating an entire new build of Livesplit with a totally different technique to achieve the same thing without re-applying each split each time you start a new run, so that's a shame. I just wanted to throw this one out there, too, though.