github-code/lvgl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(intro): fix typo (#7812)

Browse Source
This commit is contained in:
Narukara
2025-02-21 12:24:12 +08:00
committed by GitHub
parent 673e8b0d2e
commit 889f42be3f
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/intro/basics.rst
View File

@@ -138,7 +138,7 @@ when the Screen is the :ref:`active_screen`. If you want to delete the current
as you load a new one, call :cpp:func:`lv_screen_load_anim` and pass ``true`` for the as you load a new one, call :cpp:func:`lv_screen_load_anim` and pass ``true`` for the
``auto_del`` argument. If you want to keep the current Screen in RAM when you load a ``auto_del`` argument. If you want to keep the current Screen in RAM when you load a
new Screen, pass ``false`` for the ``auto_del`` argument, or call new Screen, pass ``false`` for the ``auto_del`` argument, or call
:cpp:func:`lv_screen_active` to load the new screen. :cpp:func:`lv_screen_load` to load the new screen.
A system designer is free to keep any number of Screens (and their child Widgets) in A system designer is free to keep any number of Screens (and their child Widgets) in
RAM (e.g. for quick re-display again later). Doing so: RAM (e.g. for quick re-display again later). Doing so:
@@ -159,7 +159,7 @@ Widgets are created by calling functions that look like this::
lv_<type>_create(parent) lv_<type>_create(parent)
The call will return an :cpp:type:`lv_obj_t` ``*`` pointer that can be used later to The call will return an :cpp:expr:`lv_obj_t *` pointer that can be used later to
reference the Widget to set its attributes. reference the Widget to set its attributes.
For example: For example:

8
docs/intro/introduction.rst
View File

@@ -148,13 +148,13 @@ Starting from v8, every minor release is supported for 1 year.
+---------+--------------+--------------+--------+ +---------+--------------+--------------+--------+
|v8.3 | 6 July, 2022 | 1 Jan, 2025 | Yes | |v8.3 | 6 July, 2022 | 1 Jan, 2025 | Yes |
+---------+--------------+--------------+--------+ +---------+--------------+--------------+--------+
|v8.4 | Mar 19, 2024 | Mar 20, 2025 | Yes | |v8.4 | 19 Mar, 2024 | 20 Mar, 2025 | Yes |
+---------+--------------+--------------+--------+ +---------+--------------+--------------+--------+
|v9.0 | Jan 22, 2024 | Jan 22, 2025 | Yes | |v9.0 | 22 Jan, 2024 | 22 Jan, 2025 | Yes |
+---------+--------------+--------------+--------+ +---------+--------------+--------------+--------+
|v9.1 | Mar 20, 2024 | Mar 20, 2025 | Yes | |v9.1 | 20 Mar, 2024 | 20 Mar, 2025 | Yes |
+---------+--------------+--------------+--------+ +---------+--------------+--------------+--------+
|v9.2 | Aug 26, 2024 | Aug 26, 2025 | Yes | |v9.2 | 26 Aug, 2024 | 26 Aug, 2025 | Yes |
+---------+--------------+--------------+--------+ +---------+--------------+--------------+--------+