Also, SqueezeCenter reports the following warnings: [23:13:49.9709] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [SCREENSAVER.weathertime] arrow_right => right [23:13:49.9712] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [SCREENSAVER.weathertime] arrow_down => down [23:13:49.9716] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [SCREENSAVER.weathertime] arrow_left => left [23:13:49.9719] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [SCREENSAVER.weathertime] arrow_up => up [23:13:49.9722] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [OFF.weathertime] arrow_right => right [23:13:49.9725] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [OFF.weathertime] arrow_down => down [23:13:49.9728] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [OFF.weathertime] arrow_left => left [23:13:49.9731] Slim::Hardware::IR::addModeDefaultMapping (258) ignoring [OFF.weathertime] arrow_up => up
Essentially, you are setting the button mapping actions each time the screensaver is invoked; it only needs to set the button mappings once for the mode (typically in the plugin initialisation method). Phil _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/plugins