Blocks are placed through the CLI or in perl within a plugin. Blocks have a name and unique ID; you set the name and get returned the ID when requesting a block. You can clear a block by specifying its ID. You can list current blocks and loop to clear each one. You can even, from the CLI, wipe a block without specifying its ID (a feature I consider a bug, personally) You can have a look at the readme.txt file in srvPowerControls directory, this is documented.
I haven't written a plugin, but I have running code that needs to block srvPowerControl. Blocking is very important indeed, the most common use-case is the one of a desktop running squeezeCenter: you don't want it to shutdown on you because you're not listening to music. Also, I think there is a windows gadget that blocks srvPowerControl (not sure) Perhaps a more elaborate communication could be used, where srvPowerControl announces what it wants to do and subscribed clients (plugins) can veto the change. But I doubt this is in gharris999 current plans. So for now if you wish you can fire a CLI command right after starting LazySearch. Something like "echo srvrpowerctrl clearblock nada viacli | nc -w 1 127.0.0.1 9090" will clear the topmost block. -- epoch1970 ------------------------------------------------------------------------ epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711 View this thread: http://forums.slimdevices.com/showthread.php?t=63636 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
