From 0003d6391cbf3c16daca4cd6a45632bb619342d6 Mon Sep 17 00:00:00 2001 From: Klaus Schmidinger Date: Sat, 10 Apr 2021 10:09:50 +0200 Subject: When spawning pattern timers, the new function cTimers::GetTimerForEvent() is now used to check whether a matching event already has a local timer --- HISTORY | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'HISTORY') 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"). -- cgit v1.2.3