wip: time to next

[cpvalente]

WIP

Closes #160

[cpvalente]

Hi @alex-Arc , I have started working on this with the idea that we can show in the cuesheet, the time for every event start.

I realised then that we dont have a data source to show the time when a past event has started, A work around for now is to not calculate this for events that are in the past.

I feel like the feature is confusing without the real start time data, and we are better off not releasing it until we get this What do you think?

[alex-Arc]

I dose feel confusing the way it shows up in the cue sheet. a popup might be less distracting?

[alex-Arc]

just did a quick test moving the it from the cuesheet into the right-click menu of the rundown it doesn't live update but maybe that is a good thing?

apps\client\src\features\rundown\event-block\EventBlock.tsx

  const timer = useTimer();
  const [onContextMenu] = useContextMenu<HTMLDivElement>([
    { label: `Copy ID: ${eventId}`, icon: IoCopyOutline, onClick: () => copyToClipboard(eventId) },
    //....................
    {
      label: millisToDelayString(timeStart - timer.clock) ?? '',
      icon: IoTimeOutline,
      onClick: () => console.log('test'),
      isDisabled: true,
    },
  ]);

[cpvalente]

hi @alex-Arc , thank you for trying it out. I am not particularly keen on adding the timer as a dependency to the context menu, we can workshop some other solutions

Could we narrow down what exactly does it make it confusing in the cuesheet? Is it a matter of not being able to stabilise the data as I described?

[alex-Arc]

I am not particularly keen on adding the timer as a dependency to the context menu, we can workshop some other solutions

I can understand that :)

last night I felt that the wall of timers ticking down was very distracting, it is not to bad looking at it now with fresh eyes but sill I don't know if it is good to have so many fields updating at once?

also a better name might be Planned start

[cpvalente]

but sill I don't know if it is good to have so many fields updating at once?

True. The problem to solve here is to provide a overview over how far a particular event is from starting. This wall of timers is likely what you would see in cue lab or grandMA.

Would this make more sense in the operator where there are less things?

Or perhaps we only show the time to the next element?

also a better name might be Planned start

Real start might need tweaking but Planned Start is incorrect since it should show the time to either a) the time an event will start b) the time behind for an event start (previous event running overtime) c) the time the event has started

This fields value should only be planned start if the event is in future and we are not having any delays

[alex-Arc]

This wall of timers is likely what you would see in cue lab or grandMA.

Yes although most likely only the next cue would be counting down so there isn't that much movement

Would this make more sense in the operator where there are less things?

I can see it being usefull to have in the cuesheet but adding it to the op seams like it would be more comprehensible

Or perhaps we only show the time to the next element?

No I think it is correct that we would want to be able to see it for any arbitrary event

This fields value should only be planned start if the event is in future and we are not having any delays

hmm OK then Estimated start maybe? I don't think it can be Real/Actual start until it happens

what if it was a tooltip/rightclick menu in the cuesheet? (maybe like they suggested https://github.com/cpvalente/ontime/issues/160#issue-1274876658) I don't see it so urgent to get this information that it needs to be constantly displayed or maybe it is?

[je71175]

Hi all. I agree a wall of timers would be distracting and creating pop ups are only useful for a quick look - not a countdown values when other things are happening in the show.
As a thought, would it be possible to say have the duration field clickable - and have it toggle between the duration value and the countdown to this upcoming event This way the user can select and choose to see which events display the countdown timer... thanks Jason

[cpvalente]

Thank you @je71175, good suggestion. Iterating on that, what if there was an user option Show time to where you could choose to select between "next" "5 minutes" "30 minutes" and "1 hour" as a way to minimise the amount of running timers?

The other timers would show:

• if event has started, show time it started at
• if event is planned and outside of selection margin, show fallback like ...

What do you think?

[Punkerschaf]

Hey guys, I also would like to leave some various thoughts and this:

• Finding a name: My suggestion is Log/Exp Logged/Expected. On past events it shows the logged time it startet, for future events the expected time to start based on current logging+durations.

• To limit the count of rendered times wouldn't it be the easiest to just have an option to render the next X events?

• In my opinion this is not a necessary information on the operator view. As an operator I rather need the time till I have to do something (to the next highlighted userfield on my view). But I understand this feature is a few steps in the future.

• On the cuesheet it could be helpful to show, that this is a calculated time and not editable in any way. Maybe to not draw the background box could be a small improvement, if we wan't to keep this in a separate column.

[cpvalente]

Parking this until we get the reporter going