problem with display 240x320

[pasi-konik]

I bought a 240x320 display from a store a while ago. Running Espeasy with the ST7735 driver at 172x320 resolution leaves blank frames. It works fine, but the 240x320 resolution is missing. It doesn't work with the ST7789 driver setup, and the screen is blank. The ST7796 driver displays mirrored images and inverted colors.
Can someone add a 240x320 resolution for the ST7735 driver? I'll test it.

CLK: GPIO-18
MISO: GPIO-19
MOSI: GPIO-23CS: GPIO-32
DC: GPIO-5
RES: GPIO-33
Btn: -
Bckl: : GPIO-4
ESP_Easy_mega_20250430_display_ESP32_4M316k_ETH.bin

Link to the product in the TEMU store

[tonhuisman]

Can you try a newer build from https://TD-er.nl/ESPEasy/latest ? I have included a few more resolutions recently, but not yet 320x240 for ST7735, but maybe some of the newer ST7789 320x240 (alt 1..3) drivers work for this display.

NB: That TEMU link brings me to an overview page, not to your display.

[fly74]

What is the difference between A and B in ESP_Easy_mega_20251205_display_(A/B)_ESP32_4M316k ?

[TD-er]

We split up the plugins for displays over 2 builds as those would no longer fit and you're unlikely to have multiple (different) displays at a single ESP module.
See the list of plugins: https://espeasy.readthedocs.io/en/latest/Plugin/_Plugin.html#list-of-official-plugins

[tonhuisman]

In overview terms: Display A has the TFT/Graphics (AdaGFX_Helper using) plugins removed, and Display B has most LED-based displays removed. For size reasons, as usual 🤔.

[fly74]

Great. I will test a similar Display.

[fly74]

So I have the same problem. It only work's with

but the display is 240x280. Can we make the dimensions free configurable? Or is every resolution a special case?

[tonhuisman]

I have planned to work on a migration to another graphics driver lib, that's a) actively maintained, and b) allows much more flexible configuration.
Seems like I have a planning for the coming holiday season 🤣, but no ETA 😇

[fly74]

Can you just make ST7735 with 240x280 (320) for testing? plz.

And a nice thing would be a bordervalue, because the display has rounded edges :/.

[tonhuisman]

a nice thing would be a bordervalue,

Well, you can draw a border from rules, or even from the Lines fields using the ~<gfx-command>~ syntax. That way you can be as creative as desired 😃

(Hm, I was under the impression that I had documented that feature of executing gfx-commands from Lines, somewhere, but I didn't find it yet... maybe some more typing to do on that 🤔)

[fly74]

What I tried to say was that a border would pretend text from starting in the corner like with too small resolution at the moment:

[tonhuisman]

Well, the driver can't access the pixels outside the black-background part, so there's no way possible of coloring that...

At least it's nicely centered 😸

[fly74]

:) no the centered box is because the resolution of the display is not supported. If it would, the text would start in the invisible round of the corner. If there would be a virtual box, which I could set as a border to decrease the physical resolution to a box which corner is not in the invisible area.
Hopefully described some clearer.

[tonhuisman]

If there would be a virtual box,

Look at the defwin,..., delwin,<window> and win,<window> (sub)commands in the AdaGFX Helper docs (last commands in that list). It's limited to rectangles though, no rounded corners.

[tonhuisman]

Oh, and it has the same limitation MS Windows 1.0 had. Windows can't actually overlap each other without overwriting the previously drawn window content...

[fly74]

Mine is a ST7789V2 Link but shows only with driver ST7735 a picture?!?