2008-05-04, 13:46
Wasn't sure where to put this but this seemed like the appropriate place to me.
In my skin I have a list container viewtype set up to be used with tvshow episodes specifically.
In the layout I want to have a single line, scrolling plot infolabel.
Simply like this:
Should work fine right? However when listing tv episodes, some of the plot info labels start spanning over multiple (mostly two) lines, both scrolling at the same time.
I've looked into the data on thetvdb.com of the episodes which have these problems. It appears that whenever the episode plot has a hard linebreak in it, this occurs.
I've tried several things to work around this, such as giving the label a fixed <height>, including a <wrapmultiline>false</wrapmultiline>, but no dice.
I have used the same method outside of the listview, in myvideonav.xml, and the problem occurs there too.
Tested on the latest tech build and Wiso's latest win32 build.
It seems to me that this is unintended behaviour, am I correct or is there something I should/can do about it?
I hope my explanation is understandable.
In my skin I have a list container viewtype set up to be used with tvshow episodes specifically.
In the layout I want to have a single line, scrolling plot infolabel.
Simply like this:
Code:
<control type="label">
<posx>180</posx>
<posy>110</posy>
<width>430</width>
<font>h2</font>
<align>left</align>
<scroll>true</scroll>
<textcolor>sublabel-text</textcolor>
<info>ListItem.Plot</info>
</control>Should work fine right? However when listing tv episodes, some of the plot info labels start spanning over multiple (mostly two) lines, both scrolling at the same time.
I've looked into the data on thetvdb.com of the episodes which have these problems. It appears that whenever the episode plot has a hard linebreak in it, this occurs.
I've tried several things to work around this, such as giving the label a fixed <height>, including a <wrapmultiline>false</wrapmultiline>, but no dice.
I have used the same method outside of the listview, in myvideonav.xml, and the problem occurs there too.
Tested on the latest tech build and Wiso's latest win32 build.
It seems to me that this is unintended behaviour, am I correct or is there something I should/can do about it?
I hope my explanation is understandable.
