2016-04-07, 12:50
Hi,
After reading through the wiki section regarding this([url]http://kodi.wiki/view/Addon.xml#.3Cprovides.3E_element[/url),,
it would seem that the 'provides executable; tag within 'extension' is supposed to indicate whether or not the addon is listed under programs.
My addon is a service, however to implement other features, I also call it from the settings page with arguments.
I order to avoid the 'Warning: Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.'
I add a second extension point as a python script:
However, adding that second point, even without including a 'provides executable' tag seems to cause it to be listed under Programs, for which there is no need.
Furthermore invoking it from there by clicking on it triggers an abort event and the service addon shuts down.
Is there a way to keep it from being listed or at least a way of detecting that the abort was called because the user invoked the addon from the Programs menu so it doesn't silently abort?
Thanks,
Ken
After reading through the wiki section regarding this([url]http://kodi.wiki/view/Addon.xml#.3Cprovides.3E_element[/url),,
it would seem that the 'provides executable; tag within 'extension' is supposed to indicate whether or not the addon is listed under programs.
My addon is a service, however to implement other features, I also call it from the settings page with arguments.
I order to avoid the 'Warning: Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.'
I add a second extension point as a python script:
Code:
<extension point="xbmc.service" library="default.py" start="startup">
</extension>
<extension point="xbmc.python.script" library="default.py">
</extension>
However, adding that second point, even without including a 'provides executable' tag seems to cause it to be listed under Programs, for which there is no need.
Furthermore invoking it from there by clicking on it triggers an abort event and the service addon shuts down.
Is there a way to keep it from being listed or at least a way of detecting that the abort was called because the user invoked the addon from the Programs menu so it doesn't silently abort?
Thanks,
Ken