home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Skins and Plugins Installer (MPEI)
Skin question
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1262959" data-attributes="member: 141969"><p>The old way of building panels is for the C# function to pre-define certain controls. The skin author can define the properties such as position, size, and colour for the control, but the skin author cannot access the value of the control (this is supplied by the C# function).</p><p></p><p>The new way of building panels is for relevant values to be defined as built-in skin variables, which allows the skin author to access the value and use it to control other aspects of the panel.</p><p></p><p>Most panels are a mixture of both techniques, as some constructs would be very difficult to define entirely by built-in skin variables (e.g. the list of recorded TV).</p><p></p><p>Some older panels diagnose an error if one of the pre-defined controls is missing from the xml file. This is the error that you have noticed. However, it does not necessarily mean that the panel displays wrongly, since the skin author may be using a newer built-in skin variable to provide the information, instead of the pre-defined control.</p><p></p><p>The usual way to prevent these error messages to to provide a control definition with the correct properties, but which is positioned off-screen (so that it does not affect the appearance of the panel).</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1262959, member: 141969"] The old way of building panels is for the C# function to pre-define certain controls. The skin author can define the properties such as position, size, and colour for the control, but the skin author cannot access the value of the control (this is supplied by the C# function). The new way of building panels is for relevant values to be defined as built-in skin variables, which allows the skin author to access the value and use it to control other aspects of the panel. Most panels are a mixture of both techniques, as some constructs would be very difficult to define entirely by built-in skin variables (e.g. the list of recorded TV). Some older panels diagnose an error if one of the pre-defined controls is missing from the xml file. This is the error that you have noticed. However, it does not necessarily mean that the panel displays wrongly, since the skin author may be using a newer built-in skin variable to provide the information, instead of the pre-defined control. The usual way to prevent these error messages to to provide a control definition with the correct properties, but which is positioned off-screen (so that it does not affect the appearance of the panel). -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Skins and Plugins Installer (MPEI)
Skin question
Contact us
RSS
Top
Bottom