Lines Matching refs:callback

241 In C a callback is just a function pointer. But in MicroPython we need to register a *MicroPython c…
242 callback. Therefore in the MicroPython binding we need to register both a function pointer and a Mi…
244 Therefore we defined a **callback convention** for the LVGL C API that expects lvgl headers to be d…
246 next to the function pointer when registering a callback, and access that object when the callback …
249 …to save the *MicroPython callable object* for a callback. This field must be provided when registe…
250   pointer, and provided to the callback function itself.
252 …matically keep track of the MicroPython callable object. The glue code updates it when the callback
253 …is registered, and uses it when the callback is called in order to invoke a call to the original c…
256 There are a few options for defining a callback in LVGL C API:
262 …- A pointer to that struct is provided as the **first** argument of a callback registration functi…
263     - A pointer to that struct is provided as the **first** argument of the callback itself
269     - The callback itself receives ``void *`` as the **last** argument
271 - Option 3: both callback and ``user_data`` are struct fields
278 …lso possible to mix these options, for example provide a struct pointer when registering a callback
279 (option 1) and provide ``user_data`` argument when calling the callback (options 2),
280 **as long as the same ``user_data`` that was registered is passed to the callback when it's called*…
286 …anim_t` contains ``user_data`` field. :cpp:func:`lv_anim_set_path_cb` registers `path_cb` callback.
291 …The callback :cpp:type:`lv_imgfont_get_path_cb_t` also receives the ``user_data`` as the last argu…