Lines Matching full:a
7 LVGL (Light and Versatile Graphics Library) is a free and open-source graphics
9 graphical elements, beautiful visual effects, and a low memory footprint.
67 - A **Display** or **Display Panel** is the physical hardware displaying the pixels.
68 - A :ref:`display` object is an object in RAM that represents a **Display** meant
70 - A **Screen** is the "root" Widget in the Widget Trees mentioned above, and are
71 "attached to" a particular :ref:`display`.
86 "Screen". But it is important to understand that a "Screen" is simply any
87 :ref:`Widget <widgets>` created without a parent --- the "root" of each Widget Tree.
104 user interface, an application next creates a tree of Widgets that LVGL can render to
112 To build this Widget Tree, the application first acquires a pointer to a Screen Widget.
113 A system designer is free to use the default Screen created with the :ref:`display`
114 and/or create his own. To create a new Screen Widget, simply create a Widget passing
116 most cases it is a :ref:`base_widget_overview`. (An example of another type of
117 Widget being used as a Screen is an :ref:`lv_image` Widget to supply an image for the
126 Any Widget can contain other Widgets. For example, if you want a Button to have
127 text, create a Label Widget and add it to the Button as a child.
133 - a child Widget is only visible within its parent's boundaries; any part of a child
138 as you load a new one, call :cpp:func:`lv_screen_load_anim` and pass ``true`` for the
139 ``auto_del`` argument. If you want to keep the current Screen in RAM when you load a
143 A system designer is free to keep any number of Screens (and their child Widgets) in
148 - can be handy when a Screen is complex and/or can be made the :ref:`active_screen` frequently.
224 Events are used to inform the application that something has happened with a Widget.
225 You can assign one or more callbacks to a Widget which will be called when the
228 A callback is assigned like this:
242 to invoke the callback for all events. (Beware: there are a LOT of events! This can
243 be handy for debugging or learning what events occur for a given Widget, or indeed
268 Widgets are built from one or more *parts*. For example, a button
269 has only one part called :cpp:enumerator:`LV_PART_MAIN`. However, a
273 By using parts you can apply different styles to sub-elements of a widget. (See below.)
283 Widgets can be in a combination of the following states:
295 For example, if you press a Widget it will automatically go to the
300 To check if a Widget is in a given state use
317 A style instance contains properties such as background color, border
322 using a style it needs to be initialized with :cpp:expr:`lv_style_init(&style1)`.
336 Styles are assigned using the OR-ed combination of a Widget's part and
363 styles to a part of a Widget. For example ``style_btn`` can set a
372 If a property is not set for the current state, the style with
373 :cpp:enumerator:`LV_STATE_DEFAULT` will be used. A default value is used if the
377 means if a property is not set in a Widget it will be searched for in
381 Local style properties also can be added to Widgets. This creates a
396 Themes are the default styles for Widgets. Styles from a theme are
399 The theme for your application is a compile time configuration set in
416 # Create a button with a label
440 5. Have a look at some :ref:`examples` and their code.
443 7. Read the :ref:`main_components` pages to get a better understanding of the library. (2-3 hours)
462 a LVGL has undergone normal initialization, meaning that a ``lv_display_t`` object