fixed event/live transition
This commit is contained in:
1 parent
bb99be5889
commit
881b52748e
9 files changed
+314
-2
No files matched your search
+10
@@ -3294,6 +3294,16 @@ gboolean tick(gpointer user) {
|
||||
}
|
||||
}
|
||||
|
||||
// ... and *after* it, which is the point: the block above ends in `apply_time_window()` with the
|
||||
// window the session file holds, so a restore done before it would be overwritten by the saved
|
||||
// value. The generation is the other half of the wait -- the stream's first CONFIG, which is what
|
||||
// gives the stored trigger channel a list to be found in.
|
||||
if (app->live_restore_pending && !app->replaying && !model.channels().empty() &&
|
||||
model.generation() != app->live_restore_generation) {
|
||||
app->live_restore_pending = false;
|
||||
restore_live_state(*app);
|
||||
}
|
||||
|
||||
// What the display shows, decided once for the whole frame: the producer can open or
|
||||
// close a capture between any two reads of the model, and the bind, the epoch, the pin
|
||||
// and the status line all have to describe the same picture.
|
||||
|
||||
Reference in new issue
Block a user