Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track PB's on a per-run basis #103

Closed
MichaelJBerk opened this issue Mar 3, 2021 · 0 comments
Closed

Track PB's on a per-run basis #103

MichaelJBerk opened this issue Mar 3, 2021 · 0 comments
Labels
Milestone

Comments

@MichaelJBerk
Copy link
Owner

From @jseakle #102

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.

@MichaelJBerk MichaelJBerk added this to the 4.0 milestone Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant