changelog
- Tue, 14 Aug 2018 22:57:48 -0500
- by Tuomo Valkonen <tuomov@iki.fi> [Tue, 14 Aug 2018 22:57:48 -0500] rev 116
- Pruning scheduling fix
- Fri, 16 Feb 2018 23:25:30 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Fri, 16 Feb 2018 23:25:30 +0000] rev 115
- Changed one .debug message to .info
- Wed, 14 Feb 2018 15:23:39 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Wed, 14 Feb 2018 15:23:39 +0000] rev 114
- Disable Notification Centre notifications.
They don't work reliably for some reason, and are in any case annoying
unless the display is somehow fine-tuned.
- Wed, 07 Feb 2018 20:39:01 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Wed, 07 Feb 2018 20:39:01 +0000] rev 113
- Time snapshot fixes.
Python's default arguments are purely idiotic (aka. pythonic): generated
only once. This makes sense in a purely functional language, which Python
lightyears away from, but severely limits their usefulness in an imperative
language. Decorators also seem clumsy for this, as one would have to tell
the number of positional arguments for things to work nice, being able to
pass the snapshot both positionally and as keyword. No luck.
So have to do things the old-fashioned hard way.
- Tue, 06 Feb 2018 20:55:53 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Tue, 06 Feb 2018 20:55:53 +0000] rev 112
- UI time display fixes
- Tue, 06 Feb 2018 20:16:59 +0000
- by Tuomo Valkonen <tuomov@iki.fi> [Tue, 06 Feb 2018 20:16:59 +0000] rev 111
- Changed dreamtime calculation.
The monotonic clock (time.monotonic()) sometimes advances unreliably
in sleep, so isn't reliable for calculating sleeping time. We have to
use time.time(). But this may be changed by the user, so we only use
it to track sleep periods, and still use time.monotonic() to track
wake periods.
