Open GoogleCodeExporter opened 8 years ago
No, counting *idle* time is cool. It makes sense that if I walk away from my
computer, for the Rollup to be waiting for me when I get back (if any
notifications come in in the meantime).
My proposal was specifically to not count *sleep*. In fact, thinking about it
now, waking the computer up should reset the idle timer, as anything that wakes
the machine is some form of activity.
Original comment by boredzo
on 8 Oct 2011 at 5:19
Ugh, fixed title. Thanks for fact checking.
Original comment by ch...@growl.info
on 8 Oct 2011 at 5:39
Original comment by ch...@growl.info
on 14 Nov 2011 at 12:43
Lets investigate this along with some other tweaks to idle status in 2.0 if we
have time.
Original comment by dan...@growl.info
on 1 Feb 2012 at 3:21
Growl 2.0 is getting a revamped idle detection system, this certainly could be
improved now using the new observer, and we will investigate it further (I need
to put in some logging/debugging to check what times are spat out in various
conditions so I know how to invalidate certain things).
Original comment by dan...@growl.info
on 22 Mar 2012 at 2:54
If this isn't done, go ahead and work on it after Growl 2. Otherwise, reassign
back to the 2.0 milestone and close this ticket as fixedinsource.
Original comment by ch...@growl.info
on 18 Jul 2012 at 5:24
Original comment by ch...@growl.info
on 20 Feb 2013 at 5:20
Original issue reported on code.google.com by
ch...@growl.info
on 8 Oct 2011 at 5:13