changelog
- Mon, 05 Feb 2018 18:32:36 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Mon, 05 Feb 2018 18:32:36 +0000] rev 108
- Error status wasn't correctly transmitted to UI after recent changes.
- Mon, 05 Feb 2018 18:24:30 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Mon, 05 Feb 2018 18:24:30 +0000] rev 107
- Oops, a zero retry_interval check had gone missing in scheduling reorganisation.
- Mon, 05 Feb 2018 10:25:17 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Mon, 05 Feb 2018 10:25:17 +0000] rev 106
- Added exeption protection decorators to callbacks.
If callbacks crash, there's rarely anything in the logs otherwise.
- Sun, 04 Feb 2018 14:37:09 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Sun, 04 Feb 2018 14:37:09 +0000] rev 105
- Various tray menu fixes
- Sun, 04 Feb 2018 09:38:55 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Sun, 04 Feb 2018 09:38:55 +0000] rev 104
- Added some debug log messages
- Sun, 04 Feb 2018 02:19:26 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Sun, 04 Feb 2018 02:19:26 +0000] rev 103
- Missing notify in scheduler sleep/wake callback
- Sun, 04 Feb 2018 01:36:59 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Sun, 04 Feb 2018 01:36:59 +0000] rev 102
- Changed scheduler busylooping method, and decreased precision to 5 minutes:
if there are finite-horizon events in the queue, the scheduler thread will never
sleep longer than that. This is to quickly get back on track with the schedule
when the computer wakes up from sleep, if the sleep monitor is not working or
is not implemented for the particular operating system. However, if there are
only infinite-horizon events in the queue (meaning, DreamTime-scheduled events,
and the system is sleeping or "sleeping"), the scheduler will also sleep.
Hopefully this will also help the system stay properly asleep.
