- Thread starter
- #21
So,
The problem occurs when MiniDisplay will try to parse the property #highlightedbutton from BasicHome.xml
If u remove this line then 2nd line is not being displayed, i figured this out when trying to find out which property is being used to detect button names.
So like i said some posts above it seems that MiniDisplay expects a valid name for the button to be present in BasicHome.xml and if that value is not there then it will end up displaying wrong info.
Searching deeper i found this thread LINK dated 2009.....
If u read the thread u will also see how to avoid the issue in any skin and it actually requires proper button labels in BasicHome.xml or for that matter in any menu, since MiniDisplay needs that info in order to function properly.
StreamedMP did resolve the issue back in 2009
this is why @Stéphane Lenclud cannot see the issue on his setup. The issue will appear on any display while using the MiniDisplay plugin.
@catavolt What can be done here? Currently DefaultWide has exactly the same issue since its BasicHome.xml is lacking proper button names.
The problem occurs when MiniDisplay will try to parse the property #highlightedbutton from BasicHome.xml

If u remove this line then 2nd line is not being displayed, i figured this out when trying to find out which property is being used to detect button names.
So like i said some posts above it seems that MiniDisplay expects a valid name for the button to be present in BasicHome.xml and if that value is not there then it will end up displaying wrong info.
Searching deeper i found this thread LINK dated 2009.....
If u read the thread u will also see how to avoid the issue in any skin and it actually requires proper button labels in BasicHome.xml or for that matter in any menu, since MiniDisplay needs that info in order to function properly.
StreamedMP did resolve the issue back in 2009
@catavolt What can be done here? Currently DefaultWide has exactly the same issue since its BasicHome.xml is lacking proper button names.