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
{{ message }}
This repository has been archived by the owner on Jun 16, 2018. It is now read-only.
In our competitions the scorekeeper often is the person that starts the timer. While they are waiting for the MC to do the countdown, they cannot be on the score entry screen, and this slows down their work.
Need a way to start / stop the timer from score entry page (maybe with a hot-key)
The text was updated successfully, but these errors were encountered:
I like the hot-key idea. Since all these things are controlled via message bus, maybe it is a good idea to make some kind of hotkey module that acts the same across all of the solutions (so hotkeys are the same for display system and fllscoring and so on). Therefor the apps remain separate but can still be controlled from one or the other.
We do have hotkeys for our clock application already. Also for display system it is possible to configure hotkeys. Extending it to scoring makes sense.
Note however that on touch devices hotkeys do not make much sense, so there must also be a way to do it via the ui.
Anyone for voice commands? I wouldn't pick LEGO as the trigger word though...
There is an open issue regarding the controls for the clock: FirstLegoLeague/clock#18 This should be resolved first (I'm actually not sure if this the same thing as I experienced at our Nationals, will confirm with Rob/Kenny)
We could even visualize these hotkeys like a configurable toolbar that is the same for all apps.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In our competitions the scorekeeper often is the person that starts the timer. While they are waiting for the MC to do the countdown, they cannot be on the score entry screen, and this slows down their work.
Need a way to start / stop the timer from score entry page (maybe with a hot-key)
The text was updated successfully, but these errors were encountered: