2023-01-26, 00:00
I have an addon with 2 defined extension points viz:
according to wiki that should allow the addon to be visible in both program add-ons and video add-ons. What I see in addonbrowser is it only shows up in the program add-ons node. If I select it there, the "run" button is enabled and clicking it results in the plugin.py running. Is that expected or a bug?
I then added a context menu extension point. Note that the wiki for addon.xml doesn't address this; it's on a different wiki entry. I added that extension point so:
After doing this in addonbrowser now the addon appears in context menus, program add-ons, and video add-ons, but the "run" button is disabled in all locations. Based on the wiki text about <provides> I moved the context item extension point to follow the other two:
This doesn't seem like the intended behavior?
scott s.
.
xml:<extension point="xbmc.python.script" library="default.py">
<provides>executable</provides>
</extension>
<extension point="xbmc.python.pluginsource" library="plugin.py">
<provides>video</provides>
</extension>
according to wiki that should allow the addon to be visible in both program add-ons and video add-ons. What I see in addonbrowser is it only shows up in the program add-ons node. If I select it there, the "run" button is enabled and clicking it results in the plugin.py running. Is that expected or a bug?
I then added a context menu extension point. Note that the wiki for addon.xml doesn't address this; it's on a different wiki entry. I added that extension point so:
xml:<extension point="kodi.context.item">
<menu id="kodi.core.main">
<item library="context.py">
<label>$ADDON[script.extendedinfo 32184]</label>
<visible>String.IsEqual(ListItem.dbtype,actor) | String.IsEqual(ListItem.dbtype,director)</visible>
</item>
</menu>
</extension>
<extension point="xbmc.python.script" library="default.py">
<provides>executable</provides>
</extension>
<extension point="xbmc.python.pluginsource" library="plugin.py">
<provides>video</provides>
</extension>
After doing this in addonbrowser now the addon appears in context menus, program add-ons, and video add-ons, but the "run" button is disabled in all locations. Based on the wiki text about <provides> I moved the context item extension point to follow the other two:
Now it's back to how it was originally; only shows up in program add-ons node of addonbrowser but "run" is enabled, and clicking runs the plugin plugin.py.xml:<extension point="xbmc.python.script" library="default.py">
<provides>executable</provides>
</extension>
<extension point="xbmc.python.pluginsource" library="plugin.py">
<provides>video</provides>
</extension>
<extension point="kodi.context.item">
<menu id="kodi.core.main">
<item library="context.py">
<label>$ADDON[script.extendedinfo 32184]</label>
<visible>String.IsEqual(ListItem.dbtype,actor) | String.IsEqual(ListItem.dbtype,director)</visible>
</item>
</menu>
</extension>
This doesn't seem like the intended behavior?
scott s.
.