[sualfred]

@wyrm 

Good to hear.

Why do you need 2 different buttons to install/enable it when you can do it in one? If the addon isn't installed at all, my script won't do anything. And using InstallAddon() will enable it anyway.

xml:


        <control type="radiobutton" id="$PARAM[id]03">

            <include>SettingsButton</include>

            <onclick condition="System.HasAddon(script.tv.show.next.aired)">RunScript(script.embuary.helper,action=toggleaddons,addonid=script.tv.show.next.aired,enable=false)</onclick>

            <onclick condition="!System.HasAddon(script.tv.show.next.aired)">RunScript(script.embuary.helper,action=toggleaddons,addonid=script.tv.show.next.aired,enable=true)</onclick>

            <onclick condition="!System.HasAddon(script.tv.show.next.aired)">InstallAddon(script.tv.show.next.aired)</onclick>

            <selected>System.HasAddon(script.tv.show.next.aired)</selected>

            <label>TV Show - Next Aired</label>

        </control>

I mean... it would be no problem to get this requested option, but I don't see any profit and how do you want to use this, because you would have to update the value right after you toggled its status. That's tricky and in most cases not even possible without any weird skin hacks. Convince me