Hi,
current definiton of file keymacros.conf allows simple keys to be sent to plugins only.
Example User1 @plugin_name Down Down Ok
As with vdr's new Service() interface a more flexible solution would allow sending arbitrary actions to plugins independent of plugin's menu layout.
This could be done by either reserving a special name or a special prefix character.
User1 @plugins_service service_name data_for_service
or
User1 §service_name data_for_service
Stefan Lucke wrote:
current definiton of file keymacros.conf allows simple keys to be sent to plugins only. As with vdr's new Service() interface a more flexible solution would allow sending arbitrary actions to plugins independent of plugin's menu layout.
The Service() interface is primarily designed for direct plugin-to-plugin communications, and providing complex data structures from within keymacros.conf would be really difficult.
An easier approach may be to implement a gateway to the SVDRPCommand() interface, as this interface accepts strings as command parameters.
In any case, you'll need a plugin that offers such simple calls, with static parameters and no returned information processed. Do you have any specific plugin in mind?
Cheers,
Udo
On Samstag, 12. November 2005 15:34, Udo Richter wrote:
Stefan Lucke wrote:
current definiton of file keymacros.conf allows simple keys to be sent to plugins only.
Thats is a scripting approach.
As with vdr's new Service() interface a more flexible solution would allow sending arbitrary actions to plugins independent of plugin's menu layout.
That would be a functional approach.
The Service() interface is primarily designed for direct plugin-to-plugin communications, and providing complex data structures from within keymacros.conf would be really difficult.
User1 §softdevice_keyhandler_v1.0 User1
So the receiving service can act upon vdr keys independant of plugins menu layout. Intendet action could be toggeling current crop-mode settings or full-screen vs. windowed mode. Currently output methods which implement crop mode switches have their own remote and intercept key events for doing this.
An easier approach may be to implement a gateway to the SVDRPCommand() interface, as this interface accepts strings as command parameters.
In any case, you'll need a plugin that offers such simple calls, with static parameters and no returned information processed. Do you have any specific plugin in mind?
Cheers,
Udo