Lines Matching full:with
10 In LVGL, an *lv_display_t* (not to be confused with a :ref:`Screen <screens>`) is a
28 - Have a "normal" TFT display with local UI and create "virtual" screens on VNC
56 modified with :cpp:expr:`lv_display_set_dpi(disp, new_dpi)`).
57 - 4 :ref:`screen_layers` automatically created with each display
58 - All :ref:`screens` created in association with this display (and not yet deleted---only
119 placed there with :cpp:func:`lv_indev_set_cursor`).
169 variable with the coordinates of the area to be invalidated. The area can
171 display. Usually needed with monochrome displays to invalidate ``N x 8``
202 You can create :ref:`multiple displays <multiple_displays>` with a different driver for
205 When an ``lv_display_t`` object is created, with it are created 4 Screens set up
362 of the active area can be set with
373 However with the help of :cpp:func:`lv_display_set_flush_wait_cb` a custom
386 The orientation of the display can be changed with
487 The ``color_format`` can be changed with
502 The ideal solution is configure the hardware to handle the 16 bit data with different byte order,
661 refreshing happen, for example to synchronize rendering with VSYNC or
682 consistent with the refresh period of the display to ensure that the statistical results are correc…
714 3. send the buffer's content to each real display with the truncated area.
722 With :cpp:expr:`lv_display_set_user_data(display1, p)` a custom pointer can be stored
723 with ``lv_display_t`` object. This pointer can be used later, e.g. in
732 A user's inactivity time is measured and stored with each ``lv_display_t`` object.
733 Every use of an :ref:`Input Device <indev>` (if :ref:`associated with the display