rovingcowboy wrote:well dive in on the project skin ....

rovingcowboy wrote:its always nice to have a new skinner in the group. welcome to the wonder world of wishful skinning.

drjboulder wrote:If I would have posted the entire .ini, someone would have caught it immediately and I would not have had the lesson that this little project turned into.

MoDementia wrote: If it still doesn't work
You might like to check Playlist/Max/Close Buttons pos and length(width) to make sure they aren't overlapping
[CloseButton]
[MaximizeButton]
[PlaylistButton]

monkey hi fi wrote: there is something to be said for keeping it as simple as possible., just take a break let the info soak in for a day or so then get a huge cup of coffee and try again.

rovingcowboy wrote: but you cant have the custom two load on the same line under the custom one, you have custom1 starting at 396. and going for 300 pixels long. and you have custom2 starting at 394 and going for 310 pixels long your covering up your custom1 line. it wont work.
you only need a few pixels if you want that type of thing.

drjboulder wrote:what I have good enough.

This is what I ended up using (tho, it seems like bad code to me ):

rovingcowboy wrote: just make the size=15,13 for each of the custom sections.
then place the custom2 at pixel 406
and make the code for both of them in resize =0,0,1,1 they should both resize with the right of the player but the left side of the text line should stay with that pixel that it was told to start at. if the pixel that starts the stretching part of the skin is at a location to the left of the custom sections starting pixel

when you do that if one stretches on top of the other one, just change the location for the starting pixel to the section that is on the right which would be the one that starts at 406. just move it to 415 and check the skin again, if all is fine then you got that in the right location to start with.
now go back and change the other's size to fill in the extra 9 pixels and give it a longer view area when the skin is shrunk to the small size.


i've seen your image and according to the text you have in the ini file the time counter is at location 320. it is also 64 pixels long. which would be stopping at 384. you have your custom2 starting in 394. so some place between 320 and 394 is where the skin splits and stretchs.
if you want the custom2 to stay on the left you need to move it back wards from 394 a few pixels at a time to 384 and see if it stops sliding when you stretch the skin.
if not then make the clock a little smaller, and move the custom2 over some more, do that until you find the place the custom2 section stops sliding. it is sliding because it is pinned to a pixel that is on the moving part of the skins background.

rovingcowboy wrote: here i changed the code to the numbers i said.
use it and see if the sections stay where they are and stretch to what you want.

if they do then you just have to change the stuff size of the text areas, and then the location again of the one on the right which is custom1

if the custom2 still slides to the right you need to do that backwards moving thing to find where to pin it.

Code: Select all

[Custom1] 
Type=Text 
Resizable=0,0,1,1 
Pos=406,5 
Size=15,13 
Transperent=1 
TextMask=%C4 
TextAlign=-1 
FontColor=4C5049 
FontHeight=-9 
FontName=Verdana 

[Custom2] 
Type=Text 
Resizable=0,0,1,1 
Pos=385,5 
Size=15,13 
Transperent=1 
TextMask=%A - %S 
TextAlign=0 
FontColor=4C5049 
FontHeight=-9 
FontName=Verdana 

[TimeDisplay] 
Type=Text 
Resizable=1,1,0,0 
Pos=320,5 
Size=64,13 
TextAlign=1 
Transperent=1 
TextMask=%H/%I 
SmallDigits=0 
FontColor=4C5049 
FontHeight=-9 
FontName=Verdana