You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.The text was updated successfully, but these errors were encountered: