summaryrefslogtreecommitdiff
path: root/HISTORY
diff options
context:
space:
mode:
authorKlaus Schmidinger <vdr@tvdr.de>2021-04-10 10:09:50 +0200
committerKlaus Schmidinger <vdr@tvdr.de>2021-04-10 10:09:50 +0200
commit0003d6391cbf3c16daca4cd6a45632bb619342d6 (patch)
treefed2cb559f06eea7001feca43e207597589ea93c /HISTORY
parent4e52547a59c14f619b053e2731a413221d65647f (diff)
downloadvdr-0003d6391cbf3c16daca4cd6a45632bb619342d6.tar.gz
vdr-0003d6391cbf3c16daca4cd6a45632bb619342d6.tar.bz2
When spawning pattern timers, the new function cTimers::GetTimerForEvent() is now used to check whether a matching event already has a local timer
Diffstat (limited to 'HISTORY')
-rw-r--r--HISTORY10
1 files changed, 10 insertions, 0 deletions
diff --git a/HISTORY b/HISTORY
index b20a80ef..3cda625c 100644
--- a/HISTORY
+++ b/HISTORY
@@ -9640,3 +9640,13 @@ Video Disk Recorder Revision History
by Jürgen Schneider).
- No longer switching devices for pattern timers (thanks to Helmut Binder).
- cTimer::TriggerRespawn() now only acts on local timers.
+
+2021-04-10:
+
+- When spawning pattern timers, the new function cTimers::GetTimerForEvent() is now used
+ to check whether a matching event already has a local spawned timer. Reason: creating a timer
+ from the Schedule menu (by pressing the Red button), then pressing Red again to edit
+ the timer, making it a pattern timer and moving it to a remote machine, did not cause
+ an immediate respawn on the remote machine, because at that time the event on the remote
+ machine was still covered by the initial timer (which, from the remote machine's standpoint,
+ was "remote").