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

docs(details): fix typos (#7484)

Browse Source 
Signed-off-by: bjsylvia <bjsylvia@163.com>
This commit is contained in:
bjsylvia
2024-12-20 11:06:28 +08:00
committed by GitHub
parent 019bfa4415
commit a903fc3d75
14 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/details/integration/chip/nxp.rst
View File

@@ -221,7 +221,7 @@ Basic initialization:
^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
Initialize VGLite GPU before calling :cpp:func:`lv_init()` by specifying the Initialize VGLite GPU before calling :cpp:func:`lv_init()` by specifying the
width/height of tessellation window. The default values for tesselation width width/height of tessellation window. The default values for tessellation width
and height, and command buffer size are in the SDK file "vglite_support.h". and height, and command buffer size are in the SDK file "vglite_support.h".
.. code-block:: c .. code-block:: c

4
docs/details/integration/chip/renesas.rst
View File

@@ -113,7 +113,7 @@ Get started with the Renesas ecosystem
- Browse the cloned folder and press ``Finish``. - Browse the cloned folder and press ``Finish``.
- Double click on ``configuration.xml``. This will activate the `Configuration Window`. - Double click on ``configuration.xml``. This will activate the `Configuration Window`.
Renesas' Flexible Software Package (FSP) incudes BSP and HAL layer support extended with multiple RTOS variants and other middleware stacks. Renesas' Flexible Software Package (FSP) includes BSP and HAL layer support extended with multiple RTOS variants and other middleware stacks.
The components will be available via code generation, including the entry point of *"main.c"*. The components will be available via code generation, including the entry point of *"main.c"*.
Press ``Generate Project Content`` in the top right corner. Press ``Generate Project Content`` in the top right corner.
@@ -174,7 +174,7 @@ Get started with the Renesas ecosystem
- Select the cloned folder and press ``Finish``. - Select the cloned folder and press ``Finish``.
- Double click on ``RX72N_EnVision_LVGL.scfg``. This will activate the `Configuration Window`. - Double click on ``RX72N_EnVision_LVGL.scfg``. This will activate the `Configuration Window`.
Renesas' Smart Configurator (SMC) incudes BSP and HAL layer support extended with multiple RTOS variants and other middleware stacks. Renesas' Smart Configurator (SMC) includes BSP and HAL layer support extended with multiple RTOS variants and other middleware stacks.
The components will be available via code generation, including the entry point of the application. The components will be available via code generation, including the entry point of the application.
Press ``Generate Code`` in the top right corner. Press ``Generate Code`` in the top right corner.

2
docs/details/integration/driver/display/st_ltdc.rst
View File

@@ -21,7 +21,7 @@ All permutations of the below options are well supported.
- single or double buffered - single or double buffered
- direct or partial render mode - direct or partial render mode
- OS and no OS - OS and no OS
- paralellized flushing with DMA2D (only for partial render mode) - parallelized flushing with DMA2D (only for partial render mode)
If OS is enabled, a synchronization primitive will be used to If OS is enabled, a synchronization primitive will be used to
give the thread a chance to yield to other threads while blocked, give the thread a chance to yield to other threads while blocked,

2
docs/details/integration/driver/wayland.rst
View File

@@ -62,7 +62,7 @@ An example simulator is available in this `repo <https://github.com/lvgl/lv_port
Usage Usage
----- -----
#. In ``main.c`` ``#incude "lv_drivers/wayland/wayland.h"`` #. In ``main.c`` ``#include "lv_drivers/wayland/wayland.h"``
#. Enable the Wayland driver in ``lv_conf.h`` with ``LV_USE_WAYLAND 1`` #. Enable the Wayland driver in ``lv_conf.h`` with ``LV_USE_WAYLAND 1``
#. ``LV_COLOR_DEPTH`` should be set either to ``32`` or ``16`` in ``lv_conf.h`` #. ``LV_COLOR_DEPTH`` should be set either to ``32`` or ``16`` in ``lv_conf.h``

2
docs/details/integration/os/buildroot/image_generation.rst
View File

@@ -110,7 +110,7 @@ Let's modify the configuration with ``menuconfig``.
Change these configurations: Change these configurations:
- Sytem host name to ``lvgl-buildroot`` under ``system_configuration > System hostname``. - System host name to ``lvgl-buildroot`` under ``system_configuration > System hostname``.
- Root password to ``lvgl-buildroot`` under ``system_configuration > Root password``. - Root password to ``lvgl-buildroot`` under ``system_configuration > Root password``.
- Enable SSH in ``target-packages > Networking applications > openssh`` - Enable SSH in ``target-packages > Networking applications > openssh``

8
docs/details/integration/os/yocto/lvgl_recipe.rst
View File

@@ -503,7 +503,7 @@ Compile (do_compile)
This is a optional steps, executes if compilation is available. This is a optional steps, executes if compilation is available.
If there are any compilation steps, then these steps are define in If there are any compilation steps, then these steps are define in
do_compile() funtion of bitbake. do_compile() function of bitbake.
Like in the previous task, this is handle by ``inherit cmake``. Like in the previous task, this is handle by ``inherit cmake``.
@@ -583,10 +583,10 @@ To generate an SDK of the environment, run the following command:
bitbake core-image-base -c populate_sdk bitbake core-image-base -c populate_sdk
This will create a sript ``build/tmp/deploy/sdk/ This will create a script ``build/tmp/deploy/sdk/
poky-glibc-x86_64-core-image-base-cortexa53-raspberrypi3-64-toolchain-5.0.4. poky-glibc-x86_64-core-image-base-cortexa53-raspberrypi3-64-toolchain-5.0.4.
sh``. This script allows you to install the SDK where you prefer. Here is the sh``. This script allows you to install the SDK where you prefer. Here is the
execution output of the scrips execution output of the script
.. code-block:: bash .. code-block:: bash
@@ -652,7 +652,7 @@ directory tree should look like the following
Create a recipe Create a recipe
=============== ===============
Following this structure, create a folder containing the recipies to build 1 Following this structure, create a folder containing the recipes to build 1
or multiple applications using lvgl or multiple applications using lvgl
.. code-block:: .. code-block::

4
docs/details/main-components/animation.rst
View File

@@ -46,7 +46,7 @@ Examples of the latter are: :cpp:expr:`lv_obj_set_x(widget, value)` or
:cpp:expr:`lv_obj_set_width(widget, value)`. :cpp:expr:`lv_obj_set_width(widget, value)`.
This makes it very convenient to apply to the appearance (and other attributes) of UI This makes it very convenient to apply to the appearance (and other attributes) of UI
componenets. But you can provide your own "set" functions, and so the application of components. But you can provide your own "set" functions, and so the application of
Animations is really limited only by your imagination. Animations is really limited only by your imagination.
The number of Animations that can be playing at the same time for a given object with The number of Animations that can be playing at the same time for a given object with
@@ -210,7 +210,7 @@ directions using :cpp:expr:`lv_anim_set_reverse_delay(&anim_template, delay_in_m
.. _animation_start: .. _animation_start:
Starting an Amination Starting an Animation
********************* *********************
After you have set up your :cpp:type:`lv_anim_t` object, it is important to realize After you have set up your :cpp:type:`lv_anim_t` object, it is important to realize

2
docs/details/main-components/indev.rst
View File

@@ -187,7 +187,7 @@ and ``gesture_type`` fields of the structure ``lv_indev_data_t``
/* An array that stores the collected touch events */ /* An array that stores the collected touch events */
static lv_indev_touch_data_t touches[10]; static lv_indev_touch_data_t touches[10];
/* A counter that needs to be incremented each time a touch event is recieved */ /* A counter that needs to be incremented each time a touch event is received */
static uint8_t touch_cnt; static uint8_t touch_cnt;
static void touch_read_callback(lv_indev_t * drv, lv_indev_data_t * data) static void touch_read_callback(lv_indev_t * drv, lv_indev_data_t * data)

2
docs/details/other-components/observer.rst
View File

@@ -178,7 +178,7 @@ To unsubscribe a widget from a given or all subject use:
.. code-block:: c .. code-block:: c
lv_obj_remove_from_subject(widget, subject); /* `subject` can be NULL to unsubcribe from all */ lv_obj_remove_from_subject(widget, subject); /* `subject` can be NULL to unsubscribe from all */
.. _observer_subject_groups: .. _observer_subject_groups:

2
docs/details/widgets/chart.rst
View File

@@ -92,7 +92,7 @@ Update mode
Chart layers Chart layers
------------ ------------
When a chart is drawn, certain things appear on top of other things, in this When a chart is drawn, certain things appear on top of other things, in this
oder, from back to front: order, from back to front:
- The chart's background (with optional division lines) - The chart's background (with optional division lines)
- Each data series: - Each data series:

2
docs/details/widgets/lottie.rst
View File

@@ -44,7 +44,7 @@ Set a buffer
------------ ------------
In order to render the animation a buffer needs to be assigned to the Lottie Widget. In order to render the animation a buffer needs to be assigned to the Lottie Widget.
The animations are rendered in ARGB8888 format, therefor the buffer's size should be equal to The animations are rendered in ARGB8888 format, therefore the buffer's size should be equal to
``target_width x target_height x 4`` bytes. ``target_width x target_height x 4`` bytes.
To keep the buffer size and the animation size consistent, To keep the buffer size and the animation size consistent,

2
docs/details/widgets/slider.rst
View File

@@ -47,7 +47,7 @@ Once a Slider is created, it has:
- default range of [0..100], - default range of [0..100],
- horizontal orientation, with - horizontal orientation, with
- default width of approximately 2 inches (according to configured value of :c:macro:`LV_DPI_DEF`), - default width of approximately 2 inches (according to configured value of :c:macro:`LV_DPI_DEF`),
- default hight of approximately 1/10 inch (according to configured value of :c:macro:`LV_DPI_DEF`). - default height of approximately 1/10 inch (according to configured value of :c:macro:`LV_DPI_DEF`).
To set different values use: To set different values use:

2
docs/details/widgets/switch.rst
View File

@@ -55,7 +55,7 @@ programmatically.
Change orientation Change orientation
------------------ ------------------
Swith a Switch is created, its default orientation is With a Switch is created, its default orientation is
:cpp:enumerator:`LV_SWITCH_ORIENTATION_AUTO`, which causes it to be oriented based :cpp:enumerator:`LV_SWITCH_ORIENTATION_AUTO`, which causes it to be oriented based
on ``width`` and ``height``. You can change this behavior using on ``width`` and ``height``. You can change this behavior using
:cpp:expr:`lv_switch_set_orientation(widget, orientation)`. Possible values for :cpp:expr:`lv_switch_set_orientation(widget, orientation)`. Possible values for

2
docs/details/widgets/win.rst
View File

@@ -74,7 +74,7 @@ functions can be called in any order, any number of times.
on the far right of the Header. on the far right of the Header.
- :cpp:expr:`lv_win_add_button(win, icon, button_width)` adds a Button with the - :cpp:expr:`lv_win_add_button(win, icon, button_width)` adds a Button with the
specified width that occupies the full hight of the Header (its parent). If specified width that occupies the full height of the Header (its parent). If
``icon`` is not NULL, an image is created, centered on the button, using ``icon`` ``icon`` is not NULL, an image is created, centered on the button, using ``icon``
as its image source. All valid image sources are supported, but a common source as its image source. All valid image sources are supported, but a common source
to use is one of the ``LV_SYMBOL_...`` macros, such as :c:macro:`LV_SYMBOL_CLOSE` to use is one of the ``LV_SYMBOL_...`` macros, such as :c:macro:`LV_SYMBOL_CLOSE`