OK, that's great. Very helpful. A few things are happening in the server. 1) each time the screensaver changes, slimserver treats it as a mode change, and calls the old saver/mode's "leave" function 2) each time the screensaver changes, slimserver "pushes" the new saver's mode onto the player's "modeStack", so the modeStack grows with each change 3) when you turn the player on, slimserver starts dismantling the modeStack, and calls the "leave" function for each saver/mode as it tears down the mode stack (and the "set" functions, too)
In normal behavior (without SaverSwitcher), the mode stack just wouldn't get that big. I need to look into ways to improve this -- either manipulating the modeStack in a bit of a hacked fashion, or perhaps simply using the popMode() API to trim the modeStack before changing screensavers. -- 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
