Lines Matching refs:is
8 What is a Display?
10 In LVGL, an *lv_display_t* (not to be confused with a :ref:`Screen <screens>`) is a
24 LVGL can use any number of displays. It is only limited by available RAM and MCU time.
50 it is representing, as well as other things relevant to its lifetime:
55 - DPI (default is configured :c:macro:`LV_DPI_DEF` in ``lv_conf.h``, but can be
59 one is displayed at any given time)
72 When an ``lv_display_t`` object is created, 4 permanent :ref:`screens` that
81 they contain anything that is visible) regardless of which screen is the
118 the *System Layer* is intended for system-level things (e.g. mouse cursor will be
130 If the :cpp:enumerator:`LV_OBJ_FLAG_CLICKABLE` flag is set on the Top Layer, then it will
142 Similar to the Top- and System Layers, the Bottom Layer is also the full size of the
143 Display, but it is located below the :ref:`active_screen`. It's visible only if the
144 Active Screen's background opacity is < 255.
167 - :cpp:enumerator:`LV_EVENT_INVALIDATE_AREA` An area is invalidated (marked for redraw).
174 - :cpp:enumerator:`LV_EVENT_REFR_START`: Sent when a refreshing cycle starts. Sent even if there is…
175 - :cpp:enumerator:`LV_EVENT_REFR_READY`: Sent when refreshing is ready (after rendering and calling…
177 - :cpp:enumerator:`LV_EVENT_RENDER_READY`: Sent when rendering is ready (before calling the :ref:`f…
178 - :cpp:enumerator:`LV_EVENT_FLUSH_START`: Sent before the :ref:`flush_callback` is called.
205 When an ``lv_display_t`` object is created, with it are created 4 Screens set up
214 When the first :ref:`display` object is created, it becomes the Default Display. If
242 - ``render_mode`` is one of the following:
246 buffers at least 1/10 display size is recommended. In :ref:`flush_callback` the rendered
248 button is pressed only the button's area will be redrawn.
254 only a frame buffer address needs to be changed. If a button is pressed
278 If only one buffer is used, LVGL draws the content of the screen into
280 then waits until :cpp:func:`lv_display_flush_ready` is called
281 (that is, the content of the buffer has been sent to the
288 of the other buffer is sent to the display in the background. DMA or
300 content. Once rendering is has been completed, the content of the draw buffer is
310 * screen one-by-one. `put_px` is just an example. It needs to be implemented by you. */
321 * Inform LVGL that flushing is complete so buffer can be modified again. */
332 Note that which display is targeted is passed to the function, so you can use the
338 :cpp:expr:`lv_display_flush_ready(display1)` needs to be called when flushing is
339 complete to inform LVGL that the buffer is available again to render new content
343 Callback multiple times. To see whether the current call is for the last chunk being
359 cases the physical resolution is important. For example the touchpad
377 If a Flush-Wait Callback is not set, LVGL assumes that
378 :cpp:func:`lv_display_flush_ready` is used.
387 :cpp:expr:`lv_display_set_rotation(disp, LV_DISPLAY_ROTATION_xxx)` where ``xxx`` is
390 When changing the rotation, the :cpp:enumerator:`LV_EVENT_SIZE_CHANGED` event is
401 The same is true for :cpp:enumerator:`LV_DISPLAY_RENDER_MODE_FULL`.
406 Below is an example for rotating when the rendering mode is
439 Below is an example for rotating when the rendering mode is
478 The default color format of the display is set according to :c:macro:`LV_COLOR_DEPTH`
502 The ideal solution is configure the hardware to handle the 16 bit data with different byte order,
503 however if this is not possible :cpp:expr:`lv_draw_sw_rgb565_swap(buf, buf_size_in_px)`
509 Note that this is not about swapping the Red and Blue channel but converting
527 The order of bits is MSB first, which means:
541 Ensure that the LCD controller is configured accordingly.
549 This is necessary because LVGL reserves 2 x 4 bytes in the buffer, as these are assumed to be used …
559 The :cpp:func:`lv_draw_sw_i1_convert_to_vtiled` function is used to convert a draw
561 layout. This conversion is necessary for certain display controllers that require a
573 Here is an example of how to implement and set a rounder callback:
610 a->x1 = a->x1 & (~0x1); /* Ensure x1 is even */
611 a->x2 = a->x2 | 0x1; /* Ensure x2 is odd */
624 …core can draw the screen's background while the other 3 must wait until it is finished. If there a…
632 …_tile_cnt(disp, cnt)`. The default value is :cpp:expr:`LV_DRAW_SW_DRAW_UNIT_CNT` (or 1 if software…
636 …is calculated as ``ideal_tile_size = draw_buf_size / tile_cnt``. For example, in :cpp:enumerator:`…
646 In :cpp:enumerator:`LV_DISPLAY_RENDER_MODE_DIRECT`, the screen-sized draw buffer is divided by the …
648 …DISPLAY_RENDER_MODE_FULL`, the maximum number of tiles is always created when the entire screen is…
650 …ISPLAY_RENDER_MODE_PARTIAL`, the partial buffer is divided into tiles. For example, if the draw bu…
652 …ering process, and the :ref:`flush_callback` is called once for each invalidated area. Therefore, …
681 If the performance monitor is enabled, the value of :c:macro:`LV_DEF_REFR_PERIOD` needs to be set t…
694 The parameter of :cpp:func:`lv_refr_now` is a display to refresh. If ``NULL`` is set
732 A user's inactivity time is measured and stored with each ``lv_display_t`` object.
735 activity, use :cpp:expr:`lv_display_get_inactive_time(display1)`. If ``NULL`` is
740 :cpp:expr:`lv_display_trigger_activity(display1)`. If ``display1`` is ``NULL``, the