erland;131998 Wrote:
> By reading your conversation I suspect that might want to use
> "saveRatingsForCurrentlyPlaying" instead of "saveRating" in some way.
Thank you very much for your reply, erland.
I've taken this suggestion and now am trying to call it this way from
AlarmPlugin.pm:
Code:
--------------------
'0.hold' => sub {
Plugins::TrackStat::Plugin::saveRatingsForCurrentlyPlaying(shift, undef, 0); }
--------------------
Unfortunately, it appears that the '0.hold' button is not being caught
in the AlarmPlugin
for some reason. It's still being handled by the 'common' mode which
has me
utterly confused. I thought that by defining it in the appropriate
mode
(PLUGIN.alarmactive.A, for example), that it would override the
'common' mode setting.
I'm obviously missing something here and don't quite understand the
intricacies of slimserver.
After looking at all this information, is it clear to anyone why
'0.hold' defined
in %alarmActiveFunctions is being ignored/skipped in favor of the
'common' mode definition?
Here's the debug output from d_ir:
2006-08-30 00:27:56.9676 IR: found button 2 for 768908f7
2006-08-30 00:27:56.9678 IR: found function playFavorite_2 for button
2.hold in mode common from map Default.map
2006-08-30 00:27:56.9680 irCode: playFavorite_2, 00:04:20:05:cf:57
2006-08-30 00:27:56.9689 IR: irCode not defined: playFavorite_2
2006-08-30 00:27:56.9692 IR: trying to execute button:
[playFavorite_2]
2006-08-30 00:27:56.9696 IR: executing button: playFavorite_2
--
kyleki
------------------------------------------------------------------------
kyleki's Profile: http://forums.slimdevices.com/member.php?userid=2510
View this thread: http://forums.slimdevices.com/showthread.php?t=26793
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins
