mvordeme;428547 Wrote: > Prepare to suffer ;-)! > > This is a lot more than I expected and you should only do this if you > have the time to spare. Thanks a lot for your dedication. I still need > to talk to the Lights Out developer. If there was a way SPC could > communicate with a running Lights Out service, these problems should > disappear.
There is unlikely to be a way for the Plugin to directly communicate with LightsOut. But we might be able to come up with a small windows executable that would do the job....depending on the communication method the LightsOut developer wants to pursue, e.g. sockets, named pipes, etc. This windows executable could be called as part of the shutdown/suspend/hibernate process and could essentially tell LightsOut "OK...SqueezeCenter is idle...power down if you want to." But, may I suggest you give some thought to the mechanism here? Who should do the shutting down? LightsOut? SrvrPowerCtrl? If LightsOut is in charge, then the above mechanism should work. If SrvrPowerCtrl is in charge, then LightsOut could simply create a c:\windows\temp\scp-block block file when it sees the server as "busy" and delete that file when it sees the server as idle. -- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=48521 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
