All sections - alphabetical | grouped | visual
General rules by experience:
- An image is loaded only once - with all it`s settings!
So you see only the first loaded image with it`s settings, even if you call it twice or more times with different settings. You cannot be sure which call is loaded first; the order in the skin.ini is not relevant.
The default for `Colorize=` is different for normal sections (1) and entries in [Boxes]/[Images] (0), so you have already a problem if you call an image from here and there...
The default for `Padding top/left/bottom/right=` is different for normal sections (2) and entries in [Boxes]/[Images] (0), also here you have a problem if you call an image from here and there...
But also the image type can be different than the desired... (and so on)
The only solution: make a copy of your image with another filename - for every call another copy! - Be careful with type/state subsections!
In a type-subsection like .left or .bottom you have to define every setting anew; there is nothing taken over from the main section.
But in a state-subsection like .hover or .selected the settings for Padding, Margin and Spacing are taken over from the main section (but bear in mind that also lacking entries have effect - with it`s default values).
So it is better to define all the necessary in every subsection anew, see Section types and states! - Never clone a state-subsection!
Then only the content of the subsection is taken over, but not the content of the primary main section! Eg. do not clone the [Addressbar skin.hover] to the [Mainbar skin.hover], if you do so the [Mainbar skin.hover] contains all the things from the [Addressbar skin.hover] but not the padding/margin/spacing settings from the main section [Addressbar skin] (which are otherwise automatically taken over in the [Addressbar skin.hover]).
There are also other restrictions, see Section entries! - Never trust the things you see in the standard-skin!
The standard-skin contains often settings which are not possible on the specific place and sometimes they are simply wrong...
Check once the checkbox in Opera:config-UserPrefs-DebugSkin - then you see a tooltip for every hovered skin element, containing info about the involved skin parts. That`s a great advantage - but not always helpful - in several cases it is not possible to find the things this way (but therefore you have now this guide here).
All sections - alphabetical | grouped | visual
More
Section types and states
Section entries
Defaults
Boxes | Images | Notation
Special sections Info, Options and Generic
Special headers
Fallback
General rules
Version numbers in this guide
Latest changes in this guide
Credits and links
Skin changelogs
-


