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
USER STORY: I want displays to not depend on the server for all of its timekeeping. I want the displays to be able to run their own internal clocks, and merely be kept "synchronized" with the display. This way if a display drops off the WiFi momentarily the clock can keep running internally until it reconnects to the server; otherwise, the clock "skips" and "jumps" as it gets infrequent updates from the server.
CURRENT BEHAVIOR: If the computer gets dropped from the WiFi network, even "momentarily", the display will stop updating the time. Having a local clock keeping the time will prevent the clock from not updating.
WHAT THIS WILL NOT FIX: If the display computer does not have connection when the timer is started, the timer may not start correctly.
The text was updated successfully, but these errors were encountered:
USER STORY: I want displays to not depend on the server for all of its timekeeping. I want the displays to be able to run their own internal clocks, and merely be kept "synchronized" with the display. This way if a display drops off the WiFi momentarily the clock can keep running internally until it reconnects to the server; otherwise, the clock "skips" and "jumps" as it gets infrequent updates from the server.
CURRENT BEHAVIOR: If the computer gets dropped from the WiFi network, even "momentarily", the display will stop updating the time. Having a local clock keeping the time will prevent the clock from not updating.
WHAT THIS WILL NOT FIX: If the display computer does not have connection when the timer is started, the timer may not start correctly.
The text was updated successfully, but these errors were encountered: