A number of basic functionality issues

[jseakle]

Hi! I am incredibly excited to finally see a native macos timer after all these years, truly, thank you for doing this!!

I've been using it, and it certainly works better than anything else available, which is to say, it is possible to do a speedrun with it. But there are a few things that feel very wrong:

• PBs seem to be tracked per-split rather than per-run. This is totally unlike how all major timers, and not very useful. Especially combined with the fact that undoing a split doesn't undo the change to your PB, this means that the only way to recover from pressing the split button twice by accident is to quit without saving, which is terrible. I should be open a file, start a run and do some splits, then mash Z to the beginning of the current run and save, and have there be no changes to the file.

  The normal thing is to keep a whole set of splits grouped together as a run, and then show the run with the lowest total time as the PB splits. Per-split PBs should also be tracked (i suppose as an optional column, but usually invisibly) and should be colored gold when they appear. Seeing a weird mishmash of my best ever splits in the PB column is essentially useless.

• Resetting doesn't clear the current time. There seems to be no way to get it to say 00:00 again after a run. It does start at 0 when you start a new one, but this is very strange and confusing. Also, bizarrely, resetting twice in a row reveals that the timer has kept running secretly by updating the current time.

• Clicking UI buttons doesn't remove the cursor from a title field, so i constantly find myself typing hotkeys in those by accident

• Spacebar works as a global hotkey, but doesn't work when the app is in focus

• I really, really want to be able to hide time fields with 0s in them. With both Time and PB columns visible, 6 whole extra characters worth of window width are unnecessarily forced upon me, eating into the stream real estate for the game window. If I'm doing a run that is less than an hour long, there is no reason to ever have to see those 0s. Even if the run is over an hour long, so the width is going to be there no matter what, it's pretty annoying to show all those extra 0s before the hour mark.

[MichaelJBerk]

Thanks for the input.

• Regarding PB's in particular, I'd like to try have LiveSplit-Core handle more of the backend things (such as keeping tack of PB's, etc.), which will make it much easier to implement these features in ways that more closely resemble LiveSplit and other timers.

[MichaelJBerk]

Also, to make it easier to follow, I'm going to split this into individual issues