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

Add better source for the next run(s) #84

Open
zoton2 opened this issue Apr 24, 2020 · 1 comment
Open

Add better source for the next run(s) #84

zoton2 opened this issue Apr 24, 2020 · 1 comment

Comments

@zoton2
Copy link
Contributor

zoton2 commented Apr 24, 2020

Currently we have the runDataActiveRunSurrounding which you can use to check for the next run's ID, but when you switch run it'll update, so if you were referencing this on a graphic, for example an "intermission", the next game then becomes incorrect. Currently in my bundles I wait until the timer has finished for the current run, then update the upcoming run for the intermission so it tends to be correct, but that's my own logic and I'm not sure if I should put that in this bundle or leave it out, or if there's some better logic than that.

@zoton2
Copy link
Contributor Author

zoton2 commented Apr 25, 2020

In my esa-layouts bundle, I have included extension side logic that attempts to automatically set which run is the next run (same as above but also includes a couple other safety checks), but I also have a dashboard panel that can help override that setting if needed (see screenshot below). I'm wondering if it would be useful to bring that over to this bundle?
image

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