| /lvgl-latest/src/drivers/wayland/ |
| D | lv_wayland.c | 154 struct application { struct
207 struct application * application; argument
251 static struct application application; variable
259 static struct graphic_object * create_graphic_obj(struct application * app, struct window * window,
318 struct application * app = data; in shm_format()
353 struct application * app = data; in pointer_handle_enter()
450 struct application * app = data; in pointer_handle_leave()
463 struct application * app = data; in pointer_handle_motion()
480 struct application * app = data; in pointer_handle_button()
577 window->application->wl_seat, serial, edge); in pointer_handle_button()
[all …]
|
| /lvgl-latest/docs/details/integration/os/buildroot/ |
| D | lvgl_app.rst | 1 LVGL application
5 application using LVGL running on the board.
10 Depending on the application, it might be necessary to update the rootfs. Let's
46 Generate an SDK that you can use to cross-compile the application for the
67 mkdir application && cd application
94 Build the application
97 The environment is now set up, and we're ready to build an application using
107 The application is configured to run on fbdev. You can either maintain the
110 Compile the application
140 $application.
[all …]
|
| D | quick_setup.rst | 32 The SDK is installed. Compile the application.
36 cd ../application/lv_benchmark
46 cp application/lv_benchmark/bin/lvgl-app resources/board/rootfs_overlay/usr/bin/
|
| /lvgl-latest/docs/details/integration/driver/ |
| D | X11.rst | 11 The main purpose for this driver is for testing/debugging the LVGL application in a **Linux** simul…
35 …#define LV_X11_DIRECT_EXIT 1 /* preferred default - ends the application automatically if last wi…
37 …#define LV_X11_DIRECT_EXIT 0 /* application is responsible for ending the application (e.g. by ow…
85 | Full initialisation with mouse pointer symbol and own application exit handling
114 /* set optional window close callback to enable application cleanup and exit */
|
| D | windows.rst | 10 …application in a **Windows** simulation window via **simulator mode**, or developing a standard **…
12 These are the **similarities** between simulator mode and application mode.
20 These are the **differences** between simulator mode and application mode.
32 - Designed for Windows desktop application-development scenario.
|
| D | uefi.rst | 15 …, for file system support (used to determine the file system that was used to load the application)
|
| D | wayland.rst | 13 The main purpose for this driver is for testing/debugging the LVGL application, it can also be used…
123 When this happens, it usually means that the application is minimized or hidden behind another wind…
|
| /lvgl-latest/docs/details/integration/os/ |
| D | torizon_os.rst | 9 By using docker containers it allows developers to focus on the application
13 application that can be deployed on any Toradex device running TorizonOS.
46 Toradex provides a `VSCode extension <https://developer.toradex.com/torizon/application-development…
54 …The template for a LVGL application is currently being added to the VSCode extension and will be a…
67 <https://developer.toradex.com/torizon/application-development/working-with-containers/configure-bu…
106 # Directory of the application inside container
176 Read `this article <https://developer.toradex.com/torizon/application-development/working-with-cont…
221 of the host system. While this is great for security, an embedded application will obviously need
222 `access to the hardware. <https://developer.toradex.com/torizon/application-development/use-cases/p…
224 The container running the LVGL application needs access to the framebuffer device ``/dev/fb0``.
[all …]
|
| D | zephyr.rst | 50 board, which allows for running the application on your posix compliant host system:
56 To run the application on your host:
90 This is useful for checking your application for memory leaks and other bugs.
113 they are created at application start up before :code:`main()` is executed.
147 the footprint of your application.
159 `application development guide <https://docs.zephyrproject.org/latest/develop/application/index.htm…
|
| D | qnx.rst | 84 As a general rule, if you only want to have one LVGL application in your system
95 To create a LVGL application for QNX, follow these steps in your code:
104 identical to that of a LVGL application written for any other platform.
106 The following code shows how to create a "Hello World" application:
141 Building the application consists of compiling the source with the LVGL headers,
|
| /lvgl-latest/docs/details/other-components/ |
| D | monkey.rst | 8 Testing is a technique where the user tests the application or system by providing
11 test an LVGL application.
|
| D | font_manager.rst | 36 file path and the custom font name, so that the application can access the font
105 be noted that before destruction, it is necessary to ensure that the application has
|
| D | fragment.rst | 22 fragment manager to build a navigation stack, or a multi-pane application
|
| D | xml.rst | 20 - XML files can be loaded at runtime (e.g., from an SD card) to change the application build.
53 but rather compiled into the application. The main characteristics of widgets are:
211 Widgets are written in C and compiled into the application.
|
| D | file_explorer.rst | 28 display it, send it to some other part of the application, etc..
30 event callback functions. What happens next is up to the application designer.
|
| D | obj_id.rst | 8 the application. Exactly how that happens is designed to be flexible, and can morph
9 with the needs of the application. It can even be a timestamp or other data current
|
| /lvgl-latest/src/libs/gif/ |
| D | gifdec.h | 46 void (*application)(struct _gd_GIF * gif, char id[8], char auth[3]); member
|
| D | gifdec.c | 268 else if(gif->application) { in read_application_ext()
270 gif->application(gif, app_id, app_auth_code); in read_application_ext()
|
| /lvgl-latest/docs/details/integration/boards/ |
| D | riverdi.rst | 22 it possible to embed an entire application into the device. LVGL
71 carrier board for a production application.
|
| /lvgl-latest/docs/intro/ |
| D | basics.rst | 47 After initialization, the application's job is merely to create Widget Trees when
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.
120 The application then adds Widgets to this Screen as children in the tree. Widgets
224 Events are used to inform the application that something has happened with a Widget.
244 if the application needs to process all events for some reason.)
399 The theme for your application is a compile time configuration set in
460 Below are several basic examples. They include the application code that produces
|
| /lvgl-latest/docs/details/integration/chip/ |
| D | alif.rst | 223 "High Performance". To get the best performance out of an LVGL application, select HP.
225 is that your application can run theoretically run low-priority workloads efficiently on
232 application in general, ensure the HP core is selected and the build type is release.
|
| D | renesas.rst | 25 half or to one-third, depending on the application.
178 …The components will be available via code generation, including the entry point of the application.
|
| /lvgl-latest/docs/details/debugging/ |
| D | profiler.rst | 7 As the complexity of the application increases, performance issues such as low FPS and frequent cac…
120 …ant to measure, such as scrolling a scrollable page up and down or entering/exiting an application.
|
| /lvgl-latest/demos/ |
| D | README.md | 51 4. Include "***demos/lv_demos.h***" in your application source file, for example:
|
| /lvgl-latest/docs/details/main-components/ |
| D | indev.rst | 173 The driver or application collects touch events until the indev read callback
223 An example of such an application is available in
234 in an application or web page.
266 With an encoder your application can receive events from the following:
|
