下面是一个简单的示例,用于在两个显示设备上显示不同的屏幕: voiddisp1_refresh_cb(lv_disp_drv_t*disp_drv,constlv_area_t*area,lv_color_t*color_p){// refresh display 1}voiddisp2_refresh_cb(lv_disp_drv_t*disp_drv,constlv_area_t*area,lv_color_t*color_p){// refresh display 2}voidmai...
void(*draw_ctx_init)(struct_lv_disp_drv_t*disp_drv,lv_draw_ctx_t*draw_ctx); void(*draw_ctx_deinit)(struct_lv_disp_drv_t*disp_drv,lv_draw_ctx_t*draw_ctx); size_tdraw_ctx_size; #if LV_USE_USER_DATA void*user_data;/**< Custom display driver user data*/ #endif }lv_disp_d...
lv_disp_drv_t isn't embedded in lv_disp_t directly, but many other similar driver(e.g. _lv_indev_drv_t), struct is still embedded in the corresponding device struct. My question is: what's benefit from this change? Examples and cases ...
Currently we rotate the display by swapping LV_HOR_RES_MAX and LV_VER_RES_MAX in lv_conf.h, we should use the rotated field in lv_disp_drv_t instead. Is this correct @kisvegabor, @embeddedt ? Member embeddedt commented Jul 30, 2020 rotated is a bit of a strange flag at the ...