2008-08-20, 23:57
Ooh I C!
With;
<include name="ClockBGText">
<info>System.Time(hh:mm xx)</info>
<textcolor>Highlighted</textcolor>
<include>ClockText</include>
</include>
<include name="ClockFGText">
<info>System.Time(hh:mm xx)</info>
<include>ClockText</include>
</include>
e.g xx on both the clock shadow is aligned in all languages.
On the list / infolist it could very well be a XBMC thing. When a folder is unknown which is always the case with a WEB driven plugin it defaults to list view. You can then change to infolist perfectly OK and if you come back to the same folder ie http link the skin/XBMC will remember the layout that was selected last time. My point was that infolist would be a nicer default view for any well programmed plugin. If I use Python to force infolist view I sort of kill XBMCs function of remembering the preferred view (or I have to do DB lookups to check if there is a preferred view or not)
On the script output, a big thank you.
MrZ
With;
<include name="ClockBGText">
<info>System.Time(hh:mm xx)</info>
<textcolor>Highlighted</textcolor>
<include>ClockText</include>
</include>
<include name="ClockFGText">
<info>System.Time(hh:mm xx)</info>
<include>ClockText</include>
</include>
e.g xx on both the clock shadow is aligned in all languages.
On the list / infolist it could very well be a XBMC thing. When a folder is unknown which is always the case with a WEB driven plugin it defaults to list view. You can then change to infolist perfectly OK and if you come back to the same folder ie http link the skin/XBMC will remember the layout that was selected last time. My point was that infolist would be a nicer default view for any well programmed plugin. If I use Python to force infolist view I sort of kill XBMCs function of remembering the preferred view (or I have to do DB lookups to check if there is a preferred view or not)
On the script output, a big thank you.
MrZ