I'm back again. Sorry for keep you waiting for the screenshots. I had a week full of work, but forgetting all that, go straight to the point.
1.TREE Can it be possible to add an option in main.xml to move up or down the left tree? As you can see in the image above that because the vertical splitter image there is a portion without the gray line.
What I want to achieve is to have the whole tree surrounded by the gray line, now looks like this:
You can see that the portion within the orange line has no gray line, because the image used as a vertical separator of panels (vertical splitter) is also used to separate the tree from the panels.
So, I see 2 options. Moving the tree down or define another image as vertical separator for the tree and the panel.
I've been thinking about the first option, and I must say I'm undecided. The idea I had in mind was the possibility of moving the tree down, but through main.xml, that way not harm existing or future skins,and it may look like this:
But Matt is right, this would leave an empty space. Maybe for some this is a bad thing, for me it is not.
The other option would be to define a new image as a vertical separator between the tree and the panel on the right.
2. INTERNAL MARGINS IN TREEIt would be possible to move down the scrollbar in the tree?
As you can see in the image above, the vertical up arrow's scroll bar (intentionally orange), overlaps the margin of the tree (gray line). If it were possible to define internal margins in the tree, so that this does not happen, it would be great.
3. ACTIONWINDOWIn the ActionWindow section, It would be possible to remove the solid background color, instead let the image background (just like in the second image? This is really needed for this and other two skins in which I have been working.
Again, as you can see in the image above, the color defined in main.xml as "ListBack" (intentionally pink) overlaps the background image.
if possible not to use more this defined color in all the ACTIONWINDOW backgrounds( like in the image above, but again in all the ACTIONWINDOW backgrounds) and just use the defined background image, again, it would be great.
4 and 5. TABS IN PANEL4. A icon for the new tab. So the tabs don't be confused with the links.
5. Another text color for the links.
Right now looks this way:
There is not an image that indicates where you should click to create a new tab and maybe some can not distinguish at first glance between the titles of the tabs and links. (because far as I know there's no text color defined for the text in links).
Now looks more understandable... Right?
The possibility to define color text (normal, hot) for links, and an image for new tab, please.
THE MARGIN LINE IN SOME PLACES...I must say I do not know how to call these trees / lists or something? But you see them everywhere, in the options window, when there are no tracks in Playing Now and appears PlayDoctor options, etc.. So, I think that is better a image:
I mean that margin (black line) that you can see in the image above. I noticed that the color of that line is defined in the TREE SECTION by COLOR TEXT (normal).
Could be defined separately?
7.BORDER ROW IN SPLITVIEWTABI think this is quite clear, if one defines in BorderRow 2 as number of images, you should be use the two images.
But you can see that this does not happen, ex. if I have this image (this sample is amplified):
then i put in BorderRow "NumberImages=2", should get something like this:
but this is what actually happens:
8. MENUTwo things in menu.
1.INTERNAL MARGINS.
If you have a background image with a design on the edges, should be able to define internal margins for the content, so this does not happen:
You can see in the image above, in the bottom how MenuItem does not respect the nice slightly rounded design of the background image, because the predetermined internal margins from top and bottom are not enough.
2. SEPARATOR.
These two images are self-explanatory:
WITHOUT A DEFINABLE IMAGE AS SEPARATOR
WITH A DEFINABLE IMAGE AS SEPARATOR
9. SCROLLBARThe last request is about the size of the "Arrows" (the images named as HorizontalLeftArrow, HorizontalRightArrow,etc) in scrollbars... Why always have to be square?
I mean no matter what size you give to these images, are drawn in a square. (same height-width). An example: If I define the image to height=10px and width=25px in vertical, and height=25px width=10px in horizontal, they drawn as 25x25.
And cause things like this:
When it should be like this:
And I have to ask this, because I find it disconcerting...
How are they managed the margins on images? I ask this for the following reason:
I have the following image as "MainFrame TopBorder" image:
As you can see, has "embedded" some things as track progress, some buttons and other stuffs, because, as you may know, when you design a skin with AeroGlass, images do not look like they were designed, they look more "heavy", and personally I think this is the hardest part when you make a skin with AeroGlass... modify the image until it looks "about" how it was originally designed.
Here, I was not satisfied with the results, so I chose to "embed" certain things. Then I defined the following margins for the image:
<Entry Name="TopBorder" Bitmap="MainFrame_TopBorder.png" Margins="230,25,295,0" DrawMode="REGION_H_TILE,REGION_E_VTILE,REGION_E_HTILE" />
And it looks this way:
Just like I expected. But here's the weird part... This is with Segoe UI Semibold, 9pt. When I change to other fonts (I tried only with 10) like Comic Sans, 9 pts, this happens:
Get the idea? The margins established (for define from where to where stretch/tile the image) are not respected. Why? And how to fix this?
Well, that's it. I apologize for say much but I wanted to explain my point of view the best way possible.
Thanks for reading all this.
Regards, and thanks for providing support the way they do.
Author
Topic: Some questions about Standard Skins (Read 6597 times)