lvgl_esp32_drivers icon indicating copy to clipboard operation
lvgl_esp32_drivers copied to clipboard

Synchronization of touchscreen coordinates with display orientation.

Open SinglWolf opened this issue 2 years ago • 0 comments

At the risk of being bombarded with rotten tomatoes again, but still I will speak out on this matter. The touch screen is an integral part of the display. Why should I spend just a huge amount of time synchronizing the coordinates obtained from the touchscreen with the orientation of the display? Each launch of the configuration menu results in a recompilation of the entire project. I have a fairly large project, and the laptop is as old as a mammoth. 20 minutes to compile. 6 attempts to find the right combination of touchscreen settings. 2 hours of wasted time. P.S. I don’t read any Readmi, I don’t compile screen origin tables according to screen orientation and have no idea what is “Swap XY”, “Invert X Coordinate Value”, “Invert Y Coordinate Value”. I just want to change the orientation of the display and not know the problems with the touchscreen. By the way ... the touchscreen calibration is poor. But, again, I have no idea how to properly calibrate the touchscreen the first time. Completed quest with touchscreen synchronization according to display orientation. Ahead is the quest: "Calibration of the touchscreen." If you connect another display, then ... would you be so kind as to repeat the quest: "Calibrate the touchscreen"? Some kind of surrealism. We have ESP32, on board of which there are as many as 2 mechanisms for long-term storage of user information. It is an embedded file system and a pseudo EEPROM. What prevents you from writing a set of touchscreen calibration functions by touching on the control points on the touchscreen (usually corners) and recording data using the above methods?

SinglWolf avatar Sep 27 '21 02:09 SinglWolf