Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1275827" data-attributes="member: 141969">First of all, I have never used &quot;OnlineVideos&quot;, so I cannot speak from personal experience. I can only make general comments. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />MP's skin engine allows the appearance of panels to be defined by the skin author, but mostly does not allow the skin author to vary the way that the skin engine operates. So on each panel, the skin engine will expect certain buttons or lists to be present, with specific control ids, and with specific control types. You can customise these via the tags defined for them (e.g. for a list), and you can position some controls off screen if you don't want to see them, but that is just about all that you can do for these pre-defined controls.You can add controls and buttons of your own, but generally you cannot use these to modify the behaviour of the skin engine (you have to use the pre-defined controls to do that). Example:In my skin, I allow the user to choose the number of rows that appear in the EPG and in lists. So I have added a menubutton control to enable this, but all that the menubutton does is to set a skin setting, and then the skin uses that value when calculating the layout of the EPG and lists. This menubutton does not cause the skin engine to do something different -- the button simply results in different sizes being specified for the pre-defined controls to use. This is the menubutton code:[code]&lt;control&gt;&nbsp; &lt;description&gt;&quot;List rows&quot; button&lt;/description&gt;&nbsp; &lt;type&gt;menubutton&lt;/type&gt;&nbsp; &lt;id&gt;33&lt;/id&gt;&nbsp; &lt;mode&gt;dialoglist&lt;/mode&gt;&nbsp; &lt;dialogTitle&gt;List rows&lt;/dialogTitle&gt;&nbsp; &lt;valuePrefixText&gt;List rows: &lt;/valuePrefixText&gt;&nbsp; &lt;valueTextInButton&gt;yes&lt;/valueTextInButton&gt;&nbsp; &lt;onclick&gt;#(skin.setstring('#skin.list.rows',#selectedlabel33))&lt;/onclick&gt;&nbsp; &lt;binding&gt;#skin.list.rows&lt;/binding&gt;&nbsp; &lt;subitems&gt;&nbsp; &nbsp; &lt;subitem&gt;#(3)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(4)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(5)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(6)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(7)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(8)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(9)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(10)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(11)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(12)&lt;/subitem&gt;&nbsp; &nbsp; &lt;subitem&gt;#(13)&lt;/subitem&gt;&nbsp; &lt;/subitems&gt;&nbsp; &lt;onup&gt;9&lt;/onup&gt;&nbsp; &lt;ondown&gt;6&lt;/ondown&gt;&nbsp; &lt;onleft&gt;10&lt;/onleft&gt;&nbsp; &lt;onright&gt;10&lt;/onright&gt;&lt;/control&gt;[/code]In this code:<ul>
<li data-xf-list-type="ul">onclick specifies the skin setting to be set with the value chosen by the user.</li>
<li data-xf-list-type="ul">binding specifies which skin setting contains the value to be used to highlight the current value when the menubutton list is displayed.</li>
<li data-xf-list-type="ul">subitem lists the possible values for this skin setting. In this example the user can choose any value in the range 3 to 13. Note that in this particular case I have to use expression notation to prevent the skin engine interpreting the value as a reference to a string in the language file.</li>
<li data-xf-list-type="ul">The control id is arbitrary -- you just need to choose a value that is not used by any of the pre-defined controls on that panel.</li>
</ul>This is what appears when the user clicks the &quot;List rows&quot; button in the left side menu:[ATTACH]206375[/ATTACH]So, if you want to define a value that will be used exclusively by your skin, the above code should act as an example. But you cannot add your own menubutton to modify a pre-defined control <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />. [USER=54906]@catavolt[/USER] is the skin expert, so he may be able to provide further enlightenment.-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1275827, member: 141969"] First of all, I have never used "OnlineVideos", so I cannot speak from personal experience. I can only make general comments. :( MP's skin engine allows the [i]appearance[/i] of panels to be defined by the skin author, but mostly does not allow the skin author to vary the way that the skin engine operates. So on each panel, the skin engine will expect certain buttons or lists to be present, with specific control ids, and with specific control types. You can customise these via the tags defined for them (e.g. for a list), and you can position some controls off screen if you don't want to see them, but that is just about all that you can do for these pre-defined controls. You can add controls and buttons of your own, but generally you cannot use these to modify the behaviour of the skin engine (you have to use the pre-defined controls to do that). Example: In my skin, I allow the user to choose the number of rows that appear in the EPG and in lists. So I have added a [b]menubutton[/b] control to enable this, but all that the menubutton does is to set a skin setting, and then the skin uses that value when calculating the layout of the EPG and lists. This menubutton does not cause the skin engine to do something different -- the button simply results in different sizes being specified for the pre-defined controls to use. This is the menubutton code: [code]<control> <description>"List rows" button</description> <type>menubutton</type> <id>33</id> <mode>dialoglist</mode> <dialogTitle>List rows</dialogTitle> <valuePrefixText>List rows: </valuePrefixText> <valueTextInButton>yes</valueTextInButton> <onclick>#(skin.setstring('#skin.list.rows',#selectedlabel33))</onclick> <binding>#skin.list.rows</binding> <subitems> <subitem>#(3)</subitem> <subitem>#(4)</subitem> <subitem>#(5)</subitem> <subitem>#(6)</subitem> <subitem>#(7)</subitem> <subitem>#(8)</subitem> <subitem>#(9)</subitem> <subitem>#(10)</subitem> <subitem>#(11)</subitem> <subitem>#(12)</subitem> <subitem>#(13)</subitem> </subitems> <onup>9</onup> <ondown>6</ondown> <onleft>10</onleft> <onright>10</onright> </control>[/code] In this code: [LIST] [*][b]onclick[/b] specifies the skin setting to be set with the value chosen by the user. [*][b]binding[/b] specifies which skin setting contains the value to be used to highlight the current value when the menubutton list is displayed. [*][b]subitem[/b] lists the possible values for this skin setting. In this example the user can choose any value in the range 3 to 13. Note that in this particular case I have to use expression notation to prevent the skin engine interpreting the value as a reference to a string in the language file. [*]The control id is arbitrary -- you just need to choose a value that is not used by any of the pre-defined controls on that panel. [/LIST] This is what appears when the user clicks the "List rows" button in the left side menu: [ATTACH]206375[/ATTACH] So, if you want to define a value that will be used exclusively by your skin, the above code should act as an example. But you cannot add your own menubutton to modify a pre-defined control :(. [USER=54906]@catavolt[/USER] is the skin expert, so he may be able to provide further enlightenment. -- from CyberSimian in the UK [/QUOTE]

Verification