diff options
author | Lars Henriksen <LarsHenriksen@get2net.dk> | 2019-12-11 09:57:02 +0100 |
---|---|---|
committer | Lukas Fleischer <lfleischer@calcurse.org> | 2019-12-23 13:16:39 -0500 |
commit | a0129d67510f60fadbd272252624a352f5c9f8b6 (patch) | |
tree | e56d63d3d5e9eedbf6c7f3d782609172b5d85d91 /test%2525253fid%2525253d19d2d9229e62ea5e993b462f0cdedd868ec6c2d9%25253fid%25253d04162de6ddcdbc5c1b2410f4f5f7dbae72cc62d9%253fid%253d250a233ff7aea152284e62e99b8ca09a0e032699%3fid%3da0129d67510f60fadbd272252624a352f5c9f8b6?id=a0129d67510f60fadbd272252624a352f5c9f8b6 | |
parent | b7eb9a9e941ea5e8bae7ca652fb6f16993eba30c (diff) |
Fix next recurrent appointment deleted
If the notify bar displays a recurrent appointment after midnight as next
upcoming appointment, the bar is not updated when the appointment/occurrence is
deleted. The problem is not seen in 4.3.0 because of the bug described in
commit 8cbd456, Fix next recurring appointment. The problem and the solution is
the same, this time in the function notify_same_recur_item().
Signed-off-by: Lars Henriksen <LarsHenriksen@get2net.dk>
Signed-off-by: Lukas Fleischer <lfleischer@calcurse.org>
Diffstat (limited to 'test%2525253fid%2525253d19d2d9229e62ea5e993b462f0cdedd868ec6c2d9%25253fid%25253d04162de6ddcdbc5c1b2410f4f5f7dbae72cc62d9%253fid%253d250a233ff7aea152284e62e99b8ca09a0e032699%3fid%3da0129d67510f60fadbd272252624a352f5c9f8b6?id=a0129d67510f60fadbd272252624a352f5c9f8b6')
0 files changed, 0 insertions, 0 deletions