|
|
43.
|
|
|
`name` can also be a list of variants, in which case this function returns True if any of the variants is selected.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/screens:103
|
|
|
44.
|
|
|
UI Functions
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:55
|
|
|
45.
|
|
|
The UI functions are python equivalents of the screen language statements. For each screen language statement, there is a ui function with the same name. For example, ui.text corresponds to the text statement, and ui.add corresponds to the add statement.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:57
|
|
|
46.
|
|
|
There is a simple mapping between screen language parameters and arguments and python arguments. Screen language parameters become positional arguments, while properties become keyword arguments. For example, the screen language statement: ::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:62
|
|
|
47.
|
|
|
becomes: ::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:69
|
|
|
48.
|
|
|
(It really should have an `id` parameter added.)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:73
|
|
|
49.
|
|
|
There are three groups of UI functions, corresponding to the number of children they take.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:75
|
|
|
50.
|
|
|
The following UI functions do not take any children.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:81
|
|
|
51.
|
|
|
ui.add
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:83
|
|
|
52.
|
|
|
ui.bar
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:84
|
