SumnerBoy;206048 Wrote: > 2007-06-01 09:03:02.6566 > 2007-06-01 09:03:02.6569 IR: irCode not defined: power_toggle > 2007-06-01 09:03:02.6570 IR: trying to execute button: [power_toggle] > 2007-06-01 09:03:02.6574 IR: executing button: power_toggle > 2007-06-01 09:03:02.6577 > 2007-06-01 09:03:42.5951 SaverSwitcher: 00:04:20:06:db:5f is on, but > not playing music > 2007-06-01 09:03:42.5953 SaverSwitcher: killing SaverSwitcher timer for > 00:04:20:06:db:5f since now called as a idlesaver >
Sorry for the delayed response... and the incompleteness of this post. Sometime between 09:03:02.6577 and 09:03:42.5951, the setScreensaverMode() routine for SS was called. There's very, very little code that runs between the start of the setScreensaverMode() routine and that "on, but not playing music" line. Two things I've meant to follow up on, but had trouble finding time to do so, are 1) verify that the "off" saver (RSS) is executing its leaveScreensaver() routine in that gap, too (if so, it could be causing the delay), and 2) check the Slim/Logitech code to see if there's any reason the few lines of code that SS runs in that interval might cause any sort of hang. In the 09:03:02.6577 to 09:03:42.5951 gap, did you press Power again and it not be recognized until 09:03:42.6160; or did you press another button that was never recognized, or what? Thanks, Peter -- peterw http://www.tux.org/~peterw/ free plugins: http://www.tux.org/~peterw/#slim BlankSaver BottleRocket FuzzyTime SaverSwitcher SleepFade StatusFirst VolumeLock ------------------------------------------------------------------------ peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107 View this thread: http://forums.slimdevices.com/showthread.php?t=35650 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/plugins
