Reply to thread

From observations and experimentation, my understanding is as follows:


(1) The graphics are drawn first, in the order in which their controls are encountered by the skin engine. The graphics are such things as shaded backgrounds, image backgrounds, icons, thumbnails, etc..


(2) The text is drawn next, in the order in which their controls are encountered by the skin engine. So text always overlays graphics.


(3) Video is drawn last, so video always overlays text and graphics.


In addition, there are some special cases:


(4) The pause OSD, info OSD, and zap OSD are always drawn on top of the video.


(5) The controls within an action group are treated as a separate layer, with its own graphics and text components. So:

-- The graphics in an action group overlays the text in the main panel.

-- The text in an action group overlays the graphics in the action group.


If you look at the xml files for DWHD or Titan, you will notice that the left side menu is always in an action group, and so the menu can obscure completely whatever is beneath the menu. But of course this depends on the background for the menu being 100% opaque. The opacity is controlled by the first component of the colour code: oorrggbb, where oo is the opacity expressed in hexadecimal (00 to ff). Opaque black is ff000000.


One other characteristic of an action group is visibility. The action group is hidden if the focus is on a control outside the action group. If the focus is moved to a control within the action group, the group is made visible, and then the visibility condition on each individual control within the group can take effect (e.g. to suppress those controls that you don't want to see).


-- from CyberSimian in the UK


Top Bottom