Home
last modified time | relevance | path

Searched refs:events (Results 1 – 25 of 62) sorted by relevance

123

/lvgl-latest/src/drivers/nuttx/
Dlv_nuttx_libuv.c55 static void lv_nuttx_uv_vsync_poll_cb(uv_poll_t * handle, int status, int events);
56 static void lv_nuttx_uv_disp_poll_cb(uv_poll_t * handle, int status, int events);
61 static void lv_nuttx_uv_input_poll_cb(uv_poll_t * handle, int status, int events);
184 static void lv_nuttx_uv_vsync_poll_cb(uv_poll_t * handle, int status, int events) in lv_nuttx_uv_vsync_poll_cb() argument
188 LV_UNUSED(events); in lv_nuttx_uv_vsync_poll_cb()
198 static void lv_nuttx_uv_disp_poll_cb(uv_poll_t * handle, int status, int events) in lv_nuttx_uv_disp_poll_cb() argument
203 LV_UNUSED(events); in lv_nuttx_uv_disp_poll_cb()
277 static void lv_nuttx_uv_input_poll_cb(uv_poll_t * handle, int status, int events) in lv_nuttx_uv_input_poll_cb() argument
286 if(events & UV_READABLE) { in lv_nuttx_uv_input_poll_cb()
/lvgl-latest/docs/details/base-widget/
Devent.rst15 Besides Widgets, events can registered from displays and input devices as well.
25 The user can assign callback functions to a widget to process events.
42 all the options. :cpp:enumerator:`LV_EVENT_ALL` can be used to receive all events.
55 More events can be added to a Widget, like this:
61 …d_event_cb(widget, my_event_cb_3, LV_EVENT_ALL, NULL); /* No filtering, receive all events */
71 The events will be called in the order as they were added.
75 In the very same way, events can be attached to input devices and displays like this:
105 events - Drawing events - Other events - Special events - Custom events
108 receive the *Input device*, *Drawing* and *Other* events.
110 However, the *Special events* are specific to a particular widget type.
[all …]
/lvgl-latest/docs/details/widgets/
Dlist.rst60 No special events are sent by List Widgets, but events can be sent by Buttons as usual.
66 Learn more about :ref:`events`.
Dspinner.rst46 No special events are sent by Spinner Widgets.
54 Learn more about :ref:`events`.
Dline.rst61 Only :ref:`generic events <events>` are sent by Line Widgets.
67 Learn more about :ref:`events`.
Dled.rst57 No special events are sent by LED Widgets.
63 Learn more about :ref:`events`.
Danimimg.rst53 No special events are sent by Animation-Image Widgets.
59 Learn more about :ref:`events`.
Dmsgbox.rst60 other) events to detect and act on the user's response.
109 No special events are sent by Message Box Widgets.
116 Learn more about :ref:`events`.
Dwin.rst102 No special events are sent by Window Widgets, however events can be added
109 Learn more about :ref:`events`.
Dbar.rst83 No special events are sent by Bar Widgets.
89 Learn more about :ref:`events`.
Dcanvas.rst90 No special events are sent by Canvas Widgets.
96 Learn more about :ref:`events`.
Dbutton.rst49 Learn more about :ref:`events`.
Dmenu.rst118 on the buttons so you can add events to the Menu itself.
127 Learn more about :ref:`events`.
Dlottie.rst100 No events are emitted by Lottie Widgets.
106 Learn more about :ref:`events`.
Dkeyboard.rst112 changing, sending events to the assigned text area, etc. You can remove it and replace it
125 Learn more about :ref:`events`.
Dspangroup.rst155 No special events are sent by Span Widgets.
161 Learn more about :ref:`events`.
/lvgl-latest/examples/event/
Dindex.rst14 Handle multiple events
/lvgl-latest/docs/details/debugging/
Dlog.rst18 - :c:macro:`LV_LOG_LEVEL_INFO`: Log important events
24 The events which have a higher level than the set log level will be logged
Dprofiler.rst16 LVGL has a built-in trace system to track and record the timestamps of important events that occur …
17 such as rendering events and user input events. These event timestamps serve as important metrics f…
39 …t` function with a precision of 1ms by default to obtain timestamps when events occur. Therefore, …
238 When the buffer used to store trace events becomes full, the profiler will output all the data in t…
/lvgl-latest/docs/details/integration/driver/
Dwayland.rst85 * a KEYPAD connected to Wayland keyboard events
86 * a POINTER connected to Wayland touch events
87 * a POINTER connected to Wayland pointer events
88 * an ENCODER connected to Wayland pointer axis events
Dlibinput.rst8 Libinput is an input stack for processes that need to provide events from commonly used input devic…
9 …nput handles device-specific quirks and provides an easy-to-use API to receive events from devices.
/lvgl-latest/docs/intro/
Dbasics.rst37 - fires events,
48 they are needed, manage events those Widgets generate (by way of user interaction
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
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.
/lvgl-latest/docs/details/libs/
Dffmpeg.rst46 Learn more about :ref:`events`.
/lvgl-latest/docs/details/other-components/
Dgridnav.rst59 for grid navigation. Up/down key events will be sent to the Widget that has focus.
61 for grid navigation. Left/right key events will be sent to the Widget that has focus.
/lvgl-latest/docs/details/main-components/
Dindev.rst124 prevent LVGL sending further input-device-related events.
173 The driver or application collects touch events until the indev read callback
187 /* An array that stores the collected touch events */
212 being 1:1 compatible with events emitted by the `libinput <https://wayland.freedesktop.org/libinput…
214 Handling touch events
217 Touch events are handled like any other event. First, setup a listener for the ``LV_EVENT_GESTURE``…
266 With an encoder your application can receive events from the following:
313 send key events to only one group but a group can receive data from more
338 …RESSED`, :cpp:enumerator:`LV_EVENT_CLICKED`, or :cpp:enumerator:`LV_EVENT_LONG_PRESSED` etc. events

123