Lines Matching refs:is
8 LVGL and whatever logic layer is just above it, to get and set the most important
9 properties of Widgets. It's intended use is to:
27 getting Widget properties, it is designed so minimize that additional CPU overhead.
31 What is a Widget Property?
72 This array is attached to the ``properties`` field of the Widget's class, so all
75 Some properties are read-only. When this is the case, only the ``getter`` field in
87 By default, this feature of LVGL is turned off. It can be turned on by configuring
99 An ``lv_prop_id_t`` is a :ref:`widget_property_id`, whereas an ``lv_property_t`` is a
102 The following is an example of an array that could be used as the ``values`` argument
125 :cpp:type:`lv_prop_id_t` identifies which property to get/set. It is an enum value
130 ``LV_PROPERTY_LABEL_TEXT`` is one found in ``lv_label.c``, and the properties
133 That array is attached to the Widget's class, enabling "getter" and "setter" functions
135 (Note: this is done internally so you don't have to.)
137 If the property you need to set or get using this API is not implemented yet, you can
140 "assembled" value is a 32-bit value:
149 Just make sure the ID is unique across all Widgets.
160 :cpp:type:`lv_property_t` is a struct that begins with an ``id`` field whose meaning
161 is the same as property ID described above, paired with a value, which is a union of
163 field is also capable of carrying the different value types for styles. It does this
184 * Note that place struct member `style` at first place is intended.
250 The latter two functions are useful when you already know ``name`` is among the
251 properties of a specific Widget class, or is a style name, since a property name may
260 If you need to add a property that is not present, it is recommended to add it in the
262 lists using ``./scripts/properties.py`` to ensure alphabetical ordering is preserved.