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

Ability to save each run to compare progress #14

Open
ghost opened this issue Sep 5, 2019 · 2 comments
Open

Ability to save each run to compare progress #14

ghost opened this issue Sep 5, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Sep 5, 2019

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Some way to export each run in order to import into another application or show a graph of progress.

Describe alternatives you've considered
Screenshotting the individual runs, or manually entering the data into a CSV file externally.

Additional context
The application already tracks what number attempt someone may be on. I would simply like to see the progress outside of just the PB. Say run 4 is a PB but 5 and 6 are worse, I find value in still seeing this. It will help see if one split is getting worse or the run overall.

Thanks for the hard work on this, especially the Linux compatibility.

@topeterk
Copy link
Owner

topeterk commented Sep 6, 2019

Hi, yes I think this could be a great idea to keep track of the personal progress.
The only difficulty I'm seeing is the split modification: In case one adds/move/remove splits (or even just edit the split name) it is hard to tell which split corresponds to which (previous) split in order to maintain a comparable history. Would be pretty nice to have a solution for this, otherwise the graphs are less accurate.
However one may start by ignoring this, so someone who is not editing the splits will see a comparable history anyway. And when the run gets changed then there is a "break" in the history but that eventually may not matter at the end of the day.

@ghost
Copy link
Author

ghost commented Sep 6, 2019

Yeah I did some thinking on this and you are right. Each split might be too much so perhaps just keeping the totals for each run would be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant