Difference between revisions of "GUI Themes/Specs"

Several keys in the STX syntax support the <tt>resolution</tt> property, which allows to load or skip the key and all its children when loading the theme on a given resolution.

The resolution property must contain one or more resolutions, comma separated, for which the given key is supposed to be loaded. Resolutions preceded by the minus sign will block the key from being loaded in that resolution, while resolutions without any modifiers will force the theme to be loaded in all resolutions. Here are a few examples:

/* Key will ONLY be loaded in resolutions with 320 width */

<render_info resolution = '320xY'>

/* Key will ONLY be loaded in resolutions with 240 height and in the 320x200 resolution */

 

/* Key will be loaded on ALL resolutions except for 320x200 */

<render_info resolution = '-320x200'>

 

<render_info resolution = '320xY, -240xY'>

<def var = 'TestVar' value = '200' resolution = '320xY'/>

won't fail to parse. What will happen when loading the theme using a resolution with 320 width is that <tt>TestVal</tt> first will be assigned the <tt>100</tt> value, and then it will be overwritten with the <tt>200</tt> value. On the other hand, when loading the theme using a resolution ''without'' a with of 320, the <tt>ThemeVal</tt> will be assigned the <tt>100</tt> value and the second key will be plain ignored.

<def var = 'TestVar' value = '100' resolution = '-320xY'/>

<def var = 'TestVar' value = '200' resolution = '320xY'/>

This way keys are only parsed on the resolution they are used in, but the result will be '''exactly the same''': Most of the time it's just cleaner to avoid using <tt>-320xY</tt> resolution tags, and instead write a layout that works on all resolutions and overwrite parts of it with the '320xY' tag.