mirrors/labwc
1
0
Fork 0
mirror of https://github.com/labwc/labwc.git synced 2026-04-12 08:21:13 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

[fixup]

Browse source
This commit is contained in:
Johan Malm 2024-03-24 21:29:32 +00:00
parent aa67a0bcd1
commit f4249563e8
1 changed files with 15 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/labwc-config.5.scd
View file

@ -100,19 +100,21 @@ Configuration must be wrapped in a <labwc_config> root-element like this:
decision to increase config file flexibility and keep code simple. In practical
terms, this means that `<a><b>c</b></a>` is usually equivalent to `<a b="c" />`.
However, there are some caveats:
- In menu.xml, the attributes `id` and `label` *must* be expressed as attributes
rather than as separate child tags.
- Ordering of attributes can sometimes be singificant. For example, when setting
fonts via attributes rather than children,
<font place="ActiveWindow" name="..." size="..." />
1. In menu.xml, the attributes *id*, *label* and *execute* must be
expressed as attributes rather than as separate child elements.
2. Ordering of attributes can sometimes be singificant. For example,
when setting fonts via attributes rather than children,
*<font place="ActiveWindow" name="..." size="..." />*
will set a font for active window titles, while
<font name="..." size="..." place="ActiveWindow" />
*<font name="..." size="..." place="ActiveWindow" />*
will set a font as if `place` were unspecified, because `name` and `size` will be
processed before `place`.
will set a font as if *place* were unspecified, because *name* and
*size* will be processed before *place*.
In general, it is recommended that attributes not be used to collapse more than
one level of the configuration hierarchy.