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 you can send a fullscreen message to all screens that are viewing the timer.
We would like to expand that feature, to allow users to send a message to most screen types
The UI would need to allow the user to enter a message and select from multiple possible targets.
We need to study the specifics of the design, but I suggest a list of Chips that the user can select from
From a data perspective, the user would be able to target a predefined list of screens
Hi @Dogo69Dog , the initial proposal for messages anywhere was discussed recently and met with luke-warm enthusiasm. Also note that the proposal exaggerates its value, it would be most accurate to say "messages in public / backstage and timer screens)
In short. we couldnt come up with a (good enough) use case to want to override the contents of those screens at runtime. Maybe you have an example that would change this assumption?
As for the 2 way communication, this was part of the investigation for v3.
At the time we mentioned that entertainment tools are very well served with (often unused) communication tools. With this in mind, we decided that it was not worth introducing this to ontime
Currently you can send a fullscreen message to all screens that are viewing the timer.
We would like to expand that feature, to allow users to send a message to most screen types
The UI would need to allow the user to enter a message and select from multiple possible targets.
We need to study the specifics of the design, but I suggest a list of Chips that the user can select from
From a data perspective, the user would be able to target a predefined list of screens
In the
Message Service
we can modify the data to hold a message and its targets, as well as the current blink and blackout overridesThe text was updated successfully, but these errors were encountered: