[kraqh3d]

i just corrected pm3 in cvs for those last remaining tags.

[Loto_Bak]

well i just made the prog to convert every single capitol letter to lower case.
a->a
b->b
c->c
etc...
quicker and easyer (imo)

buggers up contents of <label>mr programs</label> for example tho.

[KoTiX]

ok maybe i have just the label "about xbmc" in my skin :p

[jmarshall]

sorry about that guys - missed a few. there was a couple of others that kraqh3d missed as well (references.xml only, not important as they were mostly overridden.)

have made a couple of other changes - just cleanups:

1. removed <controloffsetx> and <controloffsety> from the settings slider as they were unused.

2. removed <subtype> from the slider - it was only set from the code.

3. removed <buddycontrolid> from spin control as it was no longer needed (was only used in the old videoosd which has been removed)

that's most of the changes i wanted to make done. please let me know if there's anything that you guys want done before 2.0 and i'll look into them.

cheers,
jonathan

[KoTiX]

hi jonathan,
i want to remember you my small request about having volume and seek bar (but also all the dialogs, overlays or osd like "player controls" or "music/video overlays"), in different positions for each screen.
what i'd really like most is that all the controls that are displayed on top of standard screens can be different in size, texture and position for each screen.
as i told you i was able to do it for the "player controls" using buttons with no textures and enabling/disabling different images depending on visibility conditions:
(eg. my stop button)

   <control>
     <description>stop button</description>
     <type>button</type>
     <id>500</id>
     <posx>586</posx>
     <posy>255</posy>
     <width>23</width>
     <height>67</height>
     <texturefocus>-</texturefocus>
     <texturenofocus>-</texturenofocus>
     <label>-</label>
     <font>-</font>
     <onleft>500</onleft>
     <onright>213</onright>
     <onup>215</onup>
     <ondown>210</ondown>
     <execute>xbmc.playercontrol(stop)</execute>
   </control>

<!-- textures for home screen active -->
   <control>
     <description>stop image</description>
     <type>image</type>
     <id>1</id>
     <posx>446</posx>
     <posy>413</posy>
     <width>25</width>
     <height>20</height>
     <texture>test-stop.png</texture>
     <visible>window.isactive(0) + control.hasfocus(500)</visible>
   </control>

<!-- textures for all other screens -->
   <control>
     <description>stop image</description>
     <type>image</type>
     <id>1</id>
     <posx>16</posx>
     <posy>93</posy>
     <width>25</width>
     <height>20</height>
     <texture>test-stop.png</texture>
     <visible>!window.isactive(0) + control.hasfocus(500)</visible>
   </control>

as you see it become a pain for all the player buttons (togglebuttons most); so how about having the possibility to enable/disable visibility to an entire group of controls, eg something like:

<!-- buttons for home screen active -->
 <controls>
 <visible>window.isactive(0)</visible>
   <control>
     <type>button</type>
     <id>402</id>
     <posx>43</posx>
     <posy>0</posy>
     <width>21</width>
     <height>22</height>
     <label>-</label>
     <texturefocus>music-stop-focus.png</texturefocus>
     <texturenofocus>music-stop-nofocus.png</texturenofocus>
     <onleft>401</onleft>
     <onright>403</onright>
     <onup>402</onup>
     <ondown>402</ondown>
     <execute>xbmc.playercontrol(stop)</execute>
   </control>

   <control>
     <type>togglebutton</type>
     <id>403</id>
     <posx>64</posx>
     <posy>0</posy>
     <width>21</width>
     <height>22</height>
     <label>-</label>
     <texturefocus>music-pause-focus.png</texturefocus>
     <texturenofocus>music-pause-nofocus.png</texturenofocus>
     <usealttexture>player.paused</usealttexture>
     <alttexturefocus>music-play-focus.png</alttexturefocus>
     <alttexturenofocus>music-play-nofocus.png</alttexturenofocus>
     <onleft>402</onleft>
     <onright>404</onright>
     <onup>403</onup>
     <ondown>403</ondown>
     <execute>xbmc.playercontrol(play)</execute>
   </control>
 </controls>


<!-- buttons for all other screens -->
 <controls>
 <visible>!window.isactive(0)</visible>
   <control>
     <type>button</type>
     <id>402</id>
     <posx>243</posx>
     <posy>400</posy>
     <width>21</width>
     <height>22</height>
     <label>-</label>
     <texturefocus>music-stop-focus2.png</texturefocus>
     <texturenofocus>music-stop-nofocus2.png</texturenofocus>
     <onleft>401</onleft>
     <onright>403</onright>
     <onup>402</onup>
     <ondown>402</ondown>
     <execute>xbmc.playercontrol(stop)</execute>
   </control>

   <control>
     <type>togglebutton</type>
     <id>403</id>
     <posx>64</posx>
     <posy>200</posy>
     <width>421</width>
     <height>22</height>
     <label>-</label>
     <texturefocus>music-pause-focus2.png</texturefocus>
     <texturenofocus>music-pause-nofocus2.png</texturenofocus>
     <usealttexture>player.paused</usealttexture>
     <alttexturefocus>music-play-focus2.png</alttexturefocus>
     <alttexturenofocus>music-play-nofocus2.png</alttexturenofocus>
     <onleft>402</onleft>
     <onright>404</onright>
     <onup>403</onup>
     <ondown>403</ondown>
     <execute>xbmc.playercontrol(play)</execute>
   </control>
 </controls>

tnx in advance as always, i hope you'll find a solution for me soon
cheers, marco.

[bakman]

perhaps a weird question , but would it be possible for the skin engine to calculate the positioning for the different screen standards, similar to the implementation with python ?

e.g one only will need to build on one standard, the rest is being handled by the engine ?

(just thinking out of the box)

[jmarshall]

kotix: will have a think about the implementation. would just being able to modify the coordinates of the dialog on a per-window basis be sufficient? i'm not sure how best to do this though. a couple of suggestions i have:

1. separate <posx>, <posy> tags dependent on the parent window. not sure the best way to implement this though, maybe something like:

<position x="25" y="25">window.isactive(5)</position>
<position x="200" y="25">true</position>

could perhaps work (with the conditions evaluated from top to bottom). trouble is that the conditionals are only really for window.isactive(), so perhaps there's a more efficient way to do it.

2. a "dialog anchor" tag in the window file:

<dialoganchor x="56" y="57">dialogsubmenu</dialoganchor>

which would set the dialogs origin at (56, 57). the posx and posy tags of the dialog would then be calculated off this, rather than off (0,0) like normal.

there's very likely other techniques that will work (and may well be simpler to understand! so please let me know if you think of any.

bakman:

the engine already supports this, and a quick look over references.xml in the ntsc and ntsc16x9 folders shows that there is very little different with the pal folders - at most 5 pixels or so difference. running xbmc in ntsc modes with these files removed (ie so that everything other than fonts is handled via the scaling off the pal coordinates) shows that there is no obvious problems as far as i can see - perhaps you guys can try as well?

if so, the proposal will be to just reduce the setup to 2 folders: one for widescreen and one for standard screen. the only difficulty then is font scaling/substitution. this could be handled in a single xml file probably.

i'm interested in all of your thoughts on this.

cheers,
jonathan

[Loto_Bak]

friendly reminder of the suggestion i mentioned on irc. exporting images (and you recommended labels) from the currently highlighted item in the listcontrol.

[FrostBox]

hello jonathan,
in first i would like to say to you that you makes a great work for xbmc.

it is possible to fix all conditionalvisibility
in the block button of the buttonscroller?

example:

<control>
<description>home button scroller</description>
<type>buttonscroller</type>
.....
<visible>!player.hasaudio | ![player.hasaudio + system.idletime(60)]</visible>
<buttons>
<button id="102">
<label>0</label>
<execute>xbmc.activatewindow(myprograms)</execute>
<visible effect="fade" time="100" start="hidden">true</visible>
</button>
<button id="104">
<label>1</label>
<execute>xbmc.activatewindow(mypictures)</execute>
<visible effect="fade" time="300" start="hidden">true</visible>
</button>
<button id="105">
<label>3</label>
<execute>xbmc.activatewindow(myvideos)</execute>
<visible effect="fade" time="500" start="hidden">true</visible>
</button>
<button id="103">
<label>2</label>
<execute>xbmc.activatewindow(mymusic)</execute>
<visible effect="fade" time="700" start="hidden">true</visible>
</button>
<button id="107">
<label>8</label>
<execute>xbmc.activatewindow(weather)</execute>
<visible effect="slide" time="900" startx="0" starty="350" accleration="1" start="hidden">true</visible>
</button>
<button id="109">
<label>5</label>
<execute>xbmc.activatewindow(500)</execute>
<visible effect="fade" time="1100" start="hidden">player.hasaudio</visible>
</button>
.....
</buttons>
</control>

thanks
frost

[Smokehead]

hi, nice to see the progress on the buttonscroller so far... i'm updating my skin from version 1.30 to 1.85.. and was testing a little with the slide effect tag on the buttonscroller, very nice effect i must say.. but still has a minor problem, when skin is loaded and buttonscroller slides in home the buttonscroller.hasfocus() does not seem to work as it should, it ends up showing no backgrounds, until i hit any button, than the bg is shown..anybody got a clue ?

my suggestion for v2.0: i always asked myself why the dailogseekbar uses a progressbar ("player.progress") to indicate the progress and the dialogvolumebar use a picture instead. why not make something like "volume.progress" possible....

[jmarshall]

frostbox:
not sure about individual visibility on the button scroller buttons - i can see the effect you are trying to accomplish, but am unsure of how to do it effectively from the code point of view. will have a think about it though, but i suspect that this is an effect you'll have to live without for now.

smokehead:
as for the buttonscroller and sliding, have you specified the "allowhiddenfocus" option on it's visibility tag? that should do what you want. if not, please supply the home.xml you are using and i'll take a look.

and yeah, volume control should be handled by the info manager - will add that one in.

cheers,
jonathan

[Smokehead]

you're right .. "allowhiddenfocus" did the job, it now works like a charm, thanks m8... you can check out the skin i'm working on right here as well the home.xml i'm using, it still has some minor issues, but i'm working on it right now... suggestions are always welcome.

another problem i have has to do with the home bg's i use (16x9main.png, 16x9main2.png), when player.has.media the buttonscroller will dissapear after 5 seconds and 16x9main2.png will load..cause this bg is more transparent..than 16x9main.png..but this does not seem to work correct, maybe you could take a look @ home.xml, and tell me what's the problem.. thanks in advance

[ceomr]

@buttonscroller -> visible tags

i think one visible tag should be considered "system has network"
better would be "system has internet"

or the possibility to deaktivate them like other buttons with "internet lookups"
because no one needs the weather button without beeing connected...

[BritneysPAIRS]

system has internet requires a ping to something like google and netowrk pluged in is instant.

[KoTiX]

ceomr,
i had the same idea for the weather button and i did it already in my skin but i've switched back to normal buttons now ("system has network" is just fine).
i was thinking to do the same for the submenu (scripts) button, is there any scripts that doesn't require a internet connection except the autoexec script?