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
The clock changes (visually) to a stop state when it reaches zero. This could also be posted on the message bus so other applications know the time has run out. For example for lights or displaysystems.
The text was updated successfully, but these errors were encountered:
Yes, perhaps we could implement something along the lines of what we discussed for scoring? There would be clock 'master' who holds the actual countdown time and send a stop signal. This would also prevent other client on the message bus to accidentally start / reset / arm the clock? This could be also only a rule when a clock has been running (ie. start signal send from a certain node, can only be stopped by that node, or overriden (confirmation)
The clock changes (visually) to a stop state when it reaches zero. This could also be posted on the message bus so other applications know the time has run out. For example for lights or displaysystems.
The text was updated successfully, but these errors were encountered: