Lines Matching refs:to
7 LVGL has a built-in Timer system. You can register a function to have it
9 :cpp:func:`lv_timer_handler`, which needs to be called every few milliseconds.
12 By default, LVGL itself uses Timers to:
21 :c:macro:`LV_DEF_REFR_PERIOD`. That Timer causes that input device to be read and
24 - update system-monitor values --- if :c:macro:`LV_USE_SYSMON` is set to ``1`` in
25 ``lv_conf.h``, one or more timers are created to periodically compute and
38 :cpp:type:`lv_timer_t` ``*`` which can be used later to modify the
40 :cpp:func:`lv_timer_create_basic` can also be used to create a new Timer without
94 When a Timer is created, its repeat-count is set to ``-1`` to cause it to repeat
100 to instead be paused after it has run ``count`` times. This can be handy if you
101 reuse that timer repeatedly and want to avoid the CPU and :cpp:func:`lv_malloc`
103 will need to set its repeat count (to either ``-1`` or a positive repeat count, since
104 it will have decremented to ``0``) and :ref:`resume <timer_pause_and_resume>` it to
129 If you are using an OS and wish to get the time the CPU is spending in an idle
131 :c:macro:`LV_USE_PERF_MONITOR` to ``1`` in ``lv_conf.h`` (if they are not already),
132 and setting the macro :c:macro:`LV_SYSMON_GET_IDLE` to the name of a function that
146 from input devices, so don't forget to re-enable it with
154 When the Timer system has been disabled (causing :cpp:func:`lv_timer_handler` to
155 return early before it has processed any timers), if you want to take some action
165 There are several cases in which you may not want to perform an action immediately.
169 - you don't want to block execution now, or
170 - you detect the need to delete a Widget in a thread other than the thread making
172 Thread>` to make all LVGL calls in a multi-threaded environment).
175 :cpp:expr:`lv_async_call(my_function, data_p)` can be used to call ``my_function`` on
177 ensures it is called in a thread in which it is safe to make LVGL calls.
178 ``data_p`` will be passed to the function when it's called. Note that only the data's
179 pointer is saved, so whatever it is pointing to needs to remain valid until the
180 function is called, so it can point to ``static``, global or dynamically allocated
181 data. If you want to cancel an asynchronous call, call
186 other than the one that normally makes LVGL calls, you are still obligated to protect
195 /* Free some resources related to `scr`*/
212 If you just want to delete a Widget and don't need to clean anything up
214 will delete the Widget on the next call to :cpp:func:`lv_timer_handler`.