fix: issue where event next was stale

cpvalente · Sep 24, 2024 · e41cdb9 · e41cdb9
1 parent 177c9a3
commit e41cdb9
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/apps/server/src/services/runtime-service/RuntimeService.ts b/apps/server/src/services/runtime-service/RuntimeService.ts
@@ -232,7 +232,7 @@ class RuntimeService {
 
  // we need to reload in a few scenarios:
  // 1. we are not confident that changes do not affect running event (eg. all events where changed)
- const safeOption = typeof affectedIds === 'undefined';
+ const safeOption = affectedIds === undefined;
  // 2. the edited event is in memory (now or next) running
  // behind conditional to avoid doing unnecessary work
  const eventInMemory = safeOption ? false : this.affectsLoaded(affectedIds);

diff --git a/apps/server/src/stores/runtimeState.ts b/apps/server/src/stores/runtimeState.ts
@@ -266,6 +266,9 @@ export function loadNext(
  return;
  }
 
+ // temporarily reset this value to simplify loop logic
+ runtimeState.eventNext = null;
+
  for (let i = eventIndex + 1; i < timedEvents.length; i++) {
  const event = timedEvents[i];
  // we dont deal with events that are not playable
@@ -360,6 +363,7 @@ export function updateAll(rundown: OntimeRundown) {
  loadNext(timedEvents);
  updateLoaded(runtimeState.eventNow ?? undefined);
  loadBlock(rundown);
+ console.log('---->', runtimeState.eventNext.note, timedEvents[1].note);
 }
 
 export function start(state: RuntimeState = runtimeState): boolean {