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
MediaPortal 1 Skins
Building a skin from scratch - a tour -
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="mbuzina" data-source="post: 1002998" data-attributes="member: 12382"><p><span style="font-size: 15px">Touch Controls?</span></p><p>That is another of the ideas I would like to include in this skin. Touch screens are more common every day - so I would like my skin to be touch enabled.</p><p> </p><p>This is unfortunately quite hard to do. So up to now I "just" have a setting in SkinSettings.xml (again ;-) which says: #skin.ShowTouchControls, a Style in reference.xml as follows:</p><p>[CODE=XML] <style Name="touchControlStyle"></p><p> <description>Touch Left</description></p><p> <id>1</id></p><p> <type>button</type></p><p> <width>20</width></p><p> <height>70</height></p><p> <visible>skin.hassetting(#skin.ShowTouchControls)</visible></p><p> <animation effect="slide" time="200" start="0,-40" easing="inout">WindowOpen</animation></p><p> <animation effect="fade" time="200" easing="inout">WindowOpen</animation></p><p> <animation effect="slide" time="200" end="0,-40" easing="inout">WindowClose</animation></p><p> <animation effect="fade" time="200" easing="inout">WindowClose</animation></p><p> </style>[/CODE]</p><p> </p><p>and some buttons designed to aid touch control (an always visible Back Button for example, a button to show the topbar and left/right nav buttons). Again there is a big but:</p><p>They don't work yet (except the back button, that is an action I can use)! The left/right buttons rely on focus moving per [CODE]<onclick>#(skin.setfocus(35,#(add(cint(1001),cint(#BasicHome.Current.ID)))))</onclick>[/CODE] but that does not work.</p><p> </p><p>The show topbar button should move focus to the topbar (which is another window) but it doesn't. Hyperlinking to window 3005 (topbar) also does not work.</p><p> </p><p>Then I wanted to finish of my topbar. I created some nice round buttons, an put them in a group with StackLayout(Horizontal,10) just to see that the buttons were aligned vertically. I was unable to create a horizontal stack, so I used the GridLayout. Again, unfortunately, GridlLayout makes each entry the same size, resulting in a too large space between the groups I wanted to create. So I ttried the TableLayout. That seems to work better, so here is my TopBar enabled BasicHome screen. Play icon & pause icon will toggle depending on playing media (since player.hasmedia is not available in # skin expressions, only in visibility settings, I had to compare #Play.Current.Title with the empty string to get a result. Still feels strange to have 2 scripts in one product). The fullscreen will also toggle as soon as I can find out if this will work correctly (compare #currentmodulefullscreenstate with the empty string?).</p><p> </p><p> </p><p> </p><p> </p><p> </p><p>[ATTACH=full]130708[/ATTACH]</p><p> </p><p>Btw.: Why does MP need 2 topbar files (topbar.xml & topbarhome.xml)? It only uses topbar.xml, the other one is ignored even on all home screens <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" /></p></blockquote><p></p>
[QUOTE="mbuzina, post: 1002998, member: 12382"] [SIZE=4]Touch Controls?[/SIZE] That is another of the ideas I would like to include in this skin. Touch screens are more common every day - so I would like my skin to be touch enabled. This is unfortunately quite hard to do. So up to now I "just" have a setting in SkinSettings.xml (again ;-) which says: #skin.ShowTouchControls, a Style in reference.xml as follows: [CODE=XML] <style Name="touchControlStyle"> <description>Touch Left</description> <id>1</id> <type>button</type> <width>20</width> <height>70</height> <visible>skin.hassetting(#skin.ShowTouchControls)</visible> <animation effect="slide" time="200" start="0,-40" easing="inout">WindowOpen</animation> <animation effect="fade" time="200" easing="inout">WindowOpen</animation> <animation effect="slide" time="200" end="0,-40" easing="inout">WindowClose</animation> <animation effect="fade" time="200" easing="inout">WindowClose</animation> </style>[/CODE] and some buttons designed to aid touch control (an always visible Back Button for example, a button to show the topbar and left/right nav buttons). Again there is a big but: They don't work yet (except the back button, that is an action I can use)! The left/right buttons rely on focus moving per [CODE]<onclick>#(skin.setfocus(35,#(add(cint(1001),cint(#BasicHome.Current.ID)))))</onclick>[/CODE] but that does not work. The show topbar button should move focus to the topbar (which is another window) but it doesn't. Hyperlinking to window 3005 (topbar) also does not work. Then I wanted to finish of my topbar. I created some nice round buttons, an put them in a group with StackLayout(Horizontal,10) just to see that the buttons were aligned vertically. I was unable to create a horizontal stack, so I used the GridLayout. Again, unfortunately, GridlLayout makes each entry the same size, resulting in a too large space between the groups I wanted to create. So I ttried the TableLayout. That seems to work better, so here is my TopBar enabled BasicHome screen. Play icon & pause icon will toggle depending on playing media (since player.hasmedia is not available in # skin expressions, only in visibility settings, I had to compare #Play.Current.Title with the empty string to get a result. Still feels strange to have 2 scripts in one product). The fullscreen will also toggle as soon as I can find out if this will work correctly (compare #currentmodulefullscreenstate with the empty string?). [ATTACH=full]130708[/ATTACH] Btw.: Why does MP need 2 topbar files (topbar.xml & topbarhome.xml)? It only uses topbar.xml, the other one is ignored even on all home screens :confused: [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Skins
Building a skin from scratch - a tour -
Contact us
RSS
Top
Bottom