Jikaru Wrote:Cool, but not exactly what I was proposing. I was actually thinking, eliminate the borderX completely, OR leaving it but Xion will determine to use the outer most edges (again by the skin only and not determined by layers) for resizing.
This means this preview (included a psd if you wanted to see layer names):
Jikaru,
What you have here is exactly what Xion does already. Instead of 'edge' the keyword to use is 'border'. If what you're proposing, is to not use keywords at all, and just let Xion determine how close something is to the edge of a skin in order to transform it into a 'border', then no, this is not a good idea.
One thing I can think of that would break that is adding shadows. Xion would allow you to resize on the shadow as its closest to the edge, this would not look so nice.
Jikaru Wrote:Without borders would resize properly, cutting the filesizes and tediousness of making a playlist, also helps to define the actual stretching/duplicated area.
As above, 'border' is the keyword instead if 'edge'
Perhaps the confusion comes from the differences between 'edge' and 'border'
'border' is used to define the resizeable parts. 'edge' is used to setup a tileable area that is constricted to a direction. So edgel means it will tile along the left side, from top to bottom. You don't need to add any 'edge' layers to your skin at all if you don't need them! Perhaps 'edge' is a bad name for it. I used it to make edges in the default skin, so it made sense there.
Jikaru Wrote:Edit: I was also thinking, that if you left out any of the tile areas in the psd that xion would just not resize in that direction, for instance:
If you left out the left one or the right one or both xion would only resize vertically and vice versa with the top tiles would only resize horizontally, and of course leaving all of them out would not resize.
I think this would efficiently erradicate the need for confusing borders/edges and be an easier way to sort where everything goes, and you could keep extra designs to the way you control snapping now.
It already does this. If you leave out a certain 'border' keyword then you won't be able to resize in that direction. If you don't use 'border' at all, you won't be able to resize the playlist.
Jikaru Wrote:Also In Xionidus 1.0 the skin I provided at the top of this page when you resize you'll notice the control buttons get split which is not what was intended. I cannot figure out how to get those to stay in the center of the skin...
Ok first of all you've build the skin in a fixed format instead of allowing Xion to know what it should tile and move around.
The first thing you need to do is break up the 'background moveable' layer in the same way that you made the 'alpha psd'. You'll also need to split up the 'moveable' layer.
Optimization tip: Your 'moveable' layer has a LOT of wasted pixels. Photoshop will save your layer as 280x309 pixels. If you split the highlights into two, Photoshop will save them as 2x(28x309). That's a saving of 224x309 pixels, or 276864 bytes of memory, and less for Xion to draw!
I'll need to look into the 'centering' of the controls. Normally to center something I would add 'anchorbl anchorbr' so that I tell Xion where to anchor (on the bottom), instead of letting it guess. However it looks like a bug in that all buttons will now be perfectly centered instead of offset slightly, so I'll look into that one.
I took about 15 minutes to modify your skin:
http://xion.r2.com.au/temp/Xionidus_pla ... iffmod.zip
So now it resizes perfectly, instead of requiring the user to resize it to the smallest possible and using it like that. It also uses less memory and less disk space. In build 112 you'll still have the issue with the playlist list offsetting itself strangely, just resize then hit F5. (This is fixed in build 113).
Take a look at the skin now and you'll see its been split up. I've used 'border' pieces to determine where the user is allowed to resize and I've used 'edge' pieces to fill parts that I want as a border, but I don't want the user to resize. (perhaps 'edge' should be renamed to 'fill')
NOTE: I left the 'left' and 'right' borders as a large area to show you what will happen. Try and resize horizontally and you will see that you can do so, on a VERY large area. Now look at the 'top' and 'bottom' border sections and you'll see that I split them up so that they're smaller areas to resize by and I used 'edge' layers with 'moveable' in order to allow the user to move the skin around with those.
I also modified the 'border' corners and just created some moveable layers as I didn't want the user to have a massive resizeable area on those either.
Cliff