davetcc wrote:TFT_eSPI is working on master, but master is not yet fully tested for all cases, we are about to do a large commit onto master within the next day or so. At that point, it will be feature complete for 2.0 and many of the in-flight issues will be fixed. Changing from one renderer to another is almost automatic in the designer UI. In 2.0, the biggest change will be the way the rendering classes work, they are skinnable at the cost of a little more memory. We need to go back and optimise this a bit for AVR, but for ESP32 it will be absolutely fine.
For ESP32 it's been through a number of tests as we have two boards and it's one of two core dev envs for me. 1. A AZdelivery DevKit dual core with an ESPprog debugger, touch screen, 320x240 display using TFT_eSPI. We also have another single core board with a similar display, rotary encoder and Adafruit for rendering. Be aware that documentation (other than Doxygen comments in code) is not ready for 2.0 yet.
You can easily switch to the 2.0 plugins in designer, change the library version stream from stable to beta from the settings. However, at that point, you'll need to get the master branch of tcMenu. And that needs 1.7.5 of IoAbstraction minimum.
I will announce here once the new beta UI is built and the tcMenu library beta code is done. It may be worth waiting a day or two for that to be honest.
Hi Dave, thank you for the early answer. Then I'll wait for the update and work with the stable 1.7 version for a few days. I really like this framework, you are doing an amazing job!
PD: Yesterday I tested the Beta 2.0 version with TFT e_SPI, I was able to test it successfully! There's a minor bug in the code generator, since it displays a "gfx" object by default when it should be "tft" as: TFT_eSPI tft;