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
Quality Assurance
Default Skins Feedback
Skin functions on opening a window
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: 1285864" data-attributes="member: 141969"><p>The control that receives the focus on entry to a panel is defined by the <defaultcontrol> tag. You can specify any id that you want -- it does not have to be 13. In my skin I use the value 1616 in "VideoFullscreen.xml". 1616 is the id of a control that I use to control the visibility of other controls. I notice that although "DefaultWideHD" uses 13, there does not seem to be a control that has that id. I guess that if the specified control does not exist, the skin engine picks a control that does exist, using some algorithm of its own.</p><p></p><p>I scanned my skin to see if I use <onfocus>, but in fact I don't use it anywhere. I have a recollection that I did try using it, but that it did not behave as I wanted in the circumstances in which I wanted to use it. But I cannot remember the details. However...</p><p></p><p>"DefaultWideHD" uses <onfocus> many times. Look at the files with names beginning "BasicHomeEditor". Most occurrences are used with "skin.setstring()", so that certainly works, but whether other skin functions can be used with <onfocus> will have to be determined by trial and error.</p><p></p><p>If you want to execute a skin function when a panel opens, you might be able to use the <define> tag at the start of the file (following <window> but before <controls>). The <define> tag is executed once when the panel opens. However, "VideoFullscreen.xml" might be a problem, since I think that logically the file is processed when video starts playing, even though there is nothing on the screen generated by the xml file. Again, trial and error will be needed to determine whether this would work. I have used the following functions in <define> tags: </p><p> cint(), add(), sub(), mul(), div(), string.trim()</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1285864, member: 141969"] The control that receives the focus on entry to a panel is defined by the <defaultcontrol> tag. You can specify any id that you want -- it does not have to be 13. In my skin I use the value 1616 in "VideoFullscreen.xml". 1616 is the id of a control that I use to control the visibility of other controls. I notice that although "DefaultWideHD" uses 13, there does not seem to be a control that has that id. I guess that if the specified control does not exist, the skin engine picks a control that does exist, using some algorithm of its own. I scanned my skin to see if I use <onfocus>, but in fact I don't use it anywhere. I have a recollection that I did try using it, but that it did not behave as I wanted in the circumstances in which I wanted to use it. But I cannot remember the details. However... "DefaultWideHD" uses <onfocus> many times. Look at the files with names beginning "BasicHomeEditor". Most occurrences are used with "skin.setstring()", so that certainly works, but whether other skin functions can be used with <onfocus> will have to be determined by trial and error. If you want to execute a skin function when a panel opens, you might be able to use the <define> tag at the start of the file (following <window> but before <controls>). The <define> tag is executed once when the panel opens. However, "VideoFullscreen.xml" might be a problem, since I think that logically the file is processed when video starts playing, even though there is nothing on the screen generated by the xml file. Again, trial and error will be needed to determine whether this would work. I have used the following functions in <define> tags: cint(), add(), sub(), mul(), div(), string.trim() -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Default Skins Feedback
Skin functions on opening a window
Contact us
RSS
Top
Bottom