From b2fb654bb333162473d0d0a3a9171b43cff7f990 Mon Sep 17 00:00:00 2001 From: Klaus Schmidinger Date: Tue, 13 Apr 2021 13:54:00 +0200 Subject: To avoid problems with very short events, non-VPS pattern timers now spawn timers for all matching events that would start while the first one is still recording --- MANUAL | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'MANUAL') diff --git a/MANUAL b/MANUAL index 640a9094..4553b78b 100644 --- a/MANUAL +++ b/MANUAL @@ -540,9 +540,9 @@ The following rules apply to pattern timers: with the given start/stop time. Overlapping events are recorded in full, even if they extend outside the given start/stop interval. - In order to actually record an event, a pattern timer "spawns" a separate timer - that does the recording. At most two timers are spawned from a pattern timer at - any given time, one for the next upcoming matching event, and one for - the event immediately following that one, in case it also matches. + that does the recording. If there are matching events that would start while + the first spawned timer is still recording (due to the start/stop margins), timers + for those events are also spawned. - Spawned timers are marked with the flag tfSpawned. - Spawned timers take the Priority, Lifetime and VPS settings from the pattern timer. - The special pattern "*" matches every event. So a timer with -- cgit v1.2.3