Lines Matching full:to
8 library providing everything you need to create an embedded GUI with easy-to-use
31 To handle touch, mouse, keypad, etc., you :ref:`create an Input Device <indev_creation>`
47 After initialization, the application's job is merely to create Widget Trees when
69 to be used by LVGL.
71 "attached to" a particular :ref:`display`.
77 Many functions related to Screen Widgets use the default display.
85 In this documentation, the term "Screen Widget" is frequently shortened to just
86 "Screen". But it is important to understand that a "Screen" is simply any
103 After LVGL is initialized (see :ref:`initializing_lvgl`), to create an interactive
104 user interface, an application next creates a tree of Widgets that LVGL can render to
109 Checkboxes, Switches, Sliders, Charts, etc. Go to :ref:`widgets` to see the full
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
117 Widget being used as a Screen is an :ref:`lv_image` Widget to supply an image for the
120 The application then adds Widgets to this Screen as children in the tree. Widgets
121 are automatically added as children to their parent Widgets at time of creation ---
122 the Widget's parent is passed as the first argument to the function that creates
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.
137 when the Screen is the :ref:`active_screen`. If you want to delete the current Screen
139 ``auto_del`` argument. If you want to keep the current Screen in RAM when you load a
141 :cpp:func:`lv_screen_active` to load the new screen.
143 A system designer is free to keep any number of Screens (and their child Widgets) in
150 If multiple Screens are maintained in RAM simultaneously, it is up to the system
151 designer as to how they are managed.
162 The call will return an :cpp:type:`lv_obj_t` ``*`` pointer that can be used later to
163 reference the Widget to set its attributes.
176 Attributes common to all Widgets are set by functions that look like this::
199 To see the full API visit the documentation of the Widget in question under
213 To delete any widget and its children::
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
242 to invoke the callback for all events. (Beware: there are a LOT of events! This can
244 if the application needs to process all events for some reason.)
260 To learn all features of the events go to the :ref:`events` section.
273 By using parts you can apply different styles to sub-elements of a widget. (See below.)
275 Read the Widget's documentation to learn which parts it uses.
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
304 To manually add or remove states use:
321 in the Widgets so they need to be defined as static or global variables. Before
322 using a style it needs to be initialized with :cpp:expr:`lv_style_init(&style1)`.
323 After that, properties can be added to configure the style. For example:
334 See :ref:`style_properties` to see the full list.
337 state. For example to use this style on the slider's indicator when the
348 … lv_obj_add_style(btn1, &style1, LV_STATE_PRESSED); /* Equal to LV_PART_MAIN | LV_STATE_PRESSED */
354 …lv_obj_add_style(slider1, &style1, LV_PART_INDICATOR); /* Equal to LV_PART_INDICATOR | LV_STATE_DE…
360 lv_obj_add_style(btn1, &style1, 0); /* Equal to LV_PART_MAIN | LV_STATE_DEFAULT */
362 Styles can be cascaded (similarly to CSS). This means you can add more
363 styles to a part of a Widget. For example ``style_btn`` can set a
365 background color to make the button red:
381 Local style properties also can be added to Widgets. This creates a
388 To learn all the features of styles see :ref:`styles`.
431 There are several good ways ways to gain deeper knowledge of LVGL. Here is one
432 recommended order of documents to read and things to play with while you are
437 2. Check out the `Online Demos`_ to see LVGL in action. (3 minutes)
441 6. Add LVGL to your project. See :ref:`add_lvgl_to_your_project` or check out
442 the `ready-to-use Projects`_.
443 7. Read the :ref:`main_components` pages to get a better understanding of the library. (2-3 hours)
444 8. Skim the documentation of :ref:`widgets` to see what is available.
445 9. If you have questions go to the `Forum`_.
446 10. Read the :ref:`contributing` guide to see how you can help to improve LVGL. (15 minutes)
450 .. _ready-to-use projects: https://github.com/lvgl?q=lv_port_&type=&language=
461 the Widget Tree needed to make LVGL render the examples shown. Each example assumes