Lines Matching refs:event

31 …lv_obj_add_event_cb(btn, my_event_cb, LV_EVENT_CLICKED, user_data);   /* Assign an event callback …
35    static void my_event_cb(lv_event_t * event)
40 In the example :cpp:enumerator:`LV_EVENT_CLICKED` means that only the click event will
41 call ``my_event_cb``. See the :ref:`list of event codes <events_codes>` for
45 data that will be available in the event.  NULL may be passed for this argument if
46 there is no need to use that data when the event is processed.  You can retrieve the
63 Even the same event callback can be used on a Widget with different
73 Other Widgets can use the same *event callback*.
104 The event codes can be grouped into these categories: - Input device
116 The following event codes exist:
132 -  :cpp:enumerator:`LV_EVENT_SCROLL_BEGIN`: Scrolling begins. The event parameter is a pointer to t…
149 -  :cpp:enumerator:`LV_EVENT_COVER_CHECK`: Check if Widget fully covers an area. The event paramete…
150 …E`: Get the required extra draw area around Widget (e.g. for shadow). The event parameter is :cpp:…
163 -  :cpp:enumerator:`LV_EVENT_INSERT`: A text is inserted to Widget. The event data is ``char `*`` b…
203 Any number of custom event codes can be registered by
213 :cpp:enumerator:`LV_EVENT_REFRESH` is a special event because it's designed to let the
245 :cpp:type:`lv_event_t` is the only parameter passed to the event callback and it
246 contains all data about the event. The following values can be gotten from it:
248 - :cpp:expr:`lv_event_get_code(e)`: get the event code
249 …v_event_get_current_target(e)`: get Widget to which an event was sent. I.e. the Widget whose event…
250 … get Widget that originally triggered the event (different from :cpp:func:`lv_event_get_target` if…
262 :cpp:enumerator:`LV_OBJ_FLAG_EVENT_BUBBLE` enabled the event will be sent to its
265 The *target* parameter of the event is always the current target Widget,
267 :cpp:expr:`lv_event_get_target_obj(e)` in the event handler.
275 .. include:: ../../examples/event/index.rst