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
Input / Output interfaces
Mini Display
Latest iMon + Minidisplay
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="jassmel" data-source="post: 1196930" data-attributes="member: 108763"><p>Hi,</p><p></p><p>i read this disussion some weeks ago, because I have the same problem using MiniDisplay plugin together with VF displays in OrigenAE HTPC cases but unfortunately the discussion stopped ~ 10weeks ago. I’m using IRTANS display and IMON, but both behave the same in combination with the new skin Default WideHD. The behavior can be verified using the Dummy Display inside MiniDisplay Plugin as proposed by Kotik some posts before. So specific display hardware is not needed.</p><p></p><p>The problem seem to be mix of MiniDisplay driver capabilities and how a skin is programmed. Going to basic home, the first line of the display is ok (“Startbildschirm”), but the second line in basic home, is displayed as “#hedit.main.use.4”. This is caused by a label defined in the file “BasicHomeEditor.main.text.xml” in line 51 inside a button control, it is not related to BasicHome.xml using no button statements as assumed before:</p><p></p><p></p><p> <control></p><p> <description>Key control</description></p><p> <id>810101</id></p><p> <type>button</type></p><p> <posX>-999</posX></p><p> <posY>-999</posY></p><p> <strong><label>#hedit.main.use.4</label> <-- content of variable will not be displayed on MiniDisplay, but the name of the variable (plain text)</strong></p><p> <textXOff>2000</textXOff></p><p> <textureFocus></textureFocus></p><p> <textureNoFocus></textureNoFocus></p><p> <hyperlink>#(string.format('{0}.hyperlink',#hedit.main.use.4))</hyperlink></p><p> <hyperlinkParameter>#(string.format('{0}.parameter',#hedit.main.use.4))</hyperlinkParameter></p><p> <action>#(string.format('{0}.action',#hedit.main.use.4))</action></p><p> <onleft>#hedit.main.backward</onleft></p><p> ………</p><p></p><p></p><p>What I found out is the following (I’m not a skin expert):</p><p></p><p>Using a variable like #hedit.main.use.4 or #highlightedbutton in conjunction with a label definition inside a button control to be handover to MiniDisplay is not working. In those cases, it will be directly show as plain text on the display. You can also put a number in (e.g. 605). In this case the text defined by an ID inside the language file (e.g. strings_de.xml) will be shown. Button lables defined with variables are shown correctly on the screen. That is the reason why the proposal of Catavolt is showing the text correctly on the screen, but not on MiniDisplay. </p><p></p><p>My Conclusion : Displaying the content of a label as variable content inside a button control on MiniDisplay is not working. One fix could be, to add this feature to MiniDisplay driver.</p><p></p><p>On the other hand using the myHome screen (see attached fotos), MiniDisplay is showing both lines correctly. But in myHome.xml seem to be realized in different way not using control buttons, but a button menue. The content of #highlightedbutton is transferred to MiniDisplay not via label statements, but in a (to be unknown) different way. I don’t think, it will be an easyone to adapt BasicHome in the same way that it is working correctly with MiniDisplay. Maybe it is easier to add a feature to MiniDisplay Driver itself. I observe that the skins of others plug-ins are also partly affected in a same manner (e.g. mywheather, HTPCInfo).</p><p></p><p></p><p>I hope this give new impulses to this topic. Maybe there are some more ideas to solve this problem.</p><p></p><p></p><p>Catavolt, can you also handover or discuss this with the programmer of MiniDisplay plugin?</p><p></p><p>Thx a lot!</p></blockquote><p></p>
[QUOTE="jassmel, post: 1196930, member: 108763"] Hi, i read this disussion some weeks ago, because I have the same problem using MiniDisplay plugin together with VF displays in OrigenAE HTPC cases but unfortunately the discussion stopped ~ 10weeks ago. I’m using IRTANS display and IMON, but both behave the same in combination with the new skin Default WideHD. The behavior can be verified using the Dummy Display inside MiniDisplay Plugin as proposed by Kotik some posts before. So specific display hardware is not needed. The problem seem to be mix of MiniDisplay driver capabilities and how a skin is programmed. Going to basic home, the first line of the display is ok (“Startbildschirm”), but the second line in basic home, is displayed as “#hedit.main.use.4”. This is caused by a label defined in the file “BasicHomeEditor.main.text.xml” in line 51 inside a button control, it is not related to BasicHome.xml using no button statements as assumed before: <control> <description>Key control</description> <id>810101</id> <type>button</type> <posX>-999</posX> <posY>-999</posY> [B]<label>#hedit.main.use.4</label> <-- content of variable will not be displayed on MiniDisplay, but the name of the variable (plain text)[/B] <textXOff>2000</textXOff> <textureFocus></textureFocus> <textureNoFocus></textureNoFocus> <hyperlink>#(string.format('{0}.hyperlink',#hedit.main.use.4))</hyperlink> <hyperlinkParameter>#(string.format('{0}.parameter',#hedit.main.use.4))</hyperlinkParameter> <action>#(string.format('{0}.action',#hedit.main.use.4))</action> <onleft>#hedit.main.backward</onleft> ……… What I found out is the following (I’m not a skin expert): Using a variable like #hedit.main.use.4 or #highlightedbutton in conjunction with a label definition inside a button control to be handover to MiniDisplay is not working. In those cases, it will be directly show as plain text on the display. You can also put a number in (e.g. 605). In this case the text defined by an ID inside the language file (e.g. strings_de.xml) will be shown. Button lables defined with variables are shown correctly on the screen. That is the reason why the proposal of Catavolt is showing the text correctly on the screen, but not on MiniDisplay. My Conclusion : Displaying the content of a label as variable content inside a button control on MiniDisplay is not working. One fix could be, to add this feature to MiniDisplay driver. On the other hand using the myHome screen (see attached fotos), MiniDisplay is showing both lines correctly. But in myHome.xml seem to be realized in different way not using control buttons, but a button menue. The content of #highlightedbutton is transferred to MiniDisplay not via label statements, but in a (to be unknown) different way. I don’t think, it will be an easyone to adapt BasicHome in the same way that it is working correctly with MiniDisplay. Maybe it is easier to add a feature to MiniDisplay Driver itself. I observe that the skins of others plug-ins are also partly affected in a same manner (e.g. mywheather, HTPCInfo). I hope this give new impulses to this topic. Maybe there are some more ideas to solve this problem. Catavolt, can you also handover or discuss this with the programmer of MiniDisplay plugin? Thx a lot! [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Input / Output interfaces
Mini Display
Latest iMon + Minidisplay
Contact us
RSS
Top
Bottom