Add warning to code and docs recommending that EspBox::initialize_touch() be called after EspBox::initialize_display().
Motivation and Context
While there are plenty of cases where users will not want to use LVGL or will want to use the touchpad for other reasons or with other systems, it's a good idea to instruct people that they will need to call initialize_touch() after initialize_display() if they want LVGL to properly recognize their touch input. Otherwise it will silently fail and LVGL will not retrieve the touch data, so no touch input will be handled by lvgl.
Description
Add warning to code and docs recommending that
EspBox::initialize_touch()
be called afterEspBox::initialize_display()
.Motivation and Context
While there are plenty of cases where users will not want to use LVGL or will want to use the touchpad for other reasons or with other systems, it's a good idea to instruct people that they will need to call
initialize_touch()
afterinitialize_display()
if they want LVGL to properly recognize their touch input. Otherwise it will silently fail and LVGL will not retrieve the touch data, so no touch input will be handled by lvgl.How has this been tested?