1,554
edits
Difference between revisions of "GUI Themes/Specs"
Describe useWithPrefix keyword
(Add XxH to evaluation precedence) |
(Describe useWithPrefix keyword) |
||
| Line 128: | Line 128: | ||
=== USE keyword === | === USE keyword === | ||
You can request loading of some particular section at any time within another section. But all variable definitions with def_ prefix get skipped. If you want to define a variable, use plain VAR= | You can request loading of some particular section at any time within another section. But all variable definitions with def_ prefix get skipped. If you want to define a variable, use plain VAR=VAL construction. | ||
Example: | Example: | ||
| Line 145: | Line 145: | ||
In this example for 320xY resolution chooser_headline and chooser_list will be loaded from [640xY] section, though buttonHeight and kLineHeight will be different. listW will get the value. | In this example for 320xY resolution chooser_headline and chooser_list will be loaded from [640xY] section, though buttonHeight and kLineHeight will be different. listW will get the value. | ||
=== USEWITHPREFIX keyword === | |||
This keyword is similiar to above described USE keyword. The difference is that all defined widgetset will get specified prefix. Example: | |||
[XxY] | |||
yoffset=10 | |||
useWithPrefix=audioControls global_ | |||
yoffset=50 | |||
useWithPrefix=audioControls game_ | |||
[audioControls] | |||
myx=10 | |||
myw=(options_dialog.w - 20) | |||
midipopup=(myx -5) yoffset (myw + 5) | |||
Here you will get global_midipopup and game_midipopup widgets defined. | |||
== Evaluation precedence == | == Evaluation precedence == | ||