Steffan

I don't want to be a party pooper, but it required some "hacking" to get to what you see there. At the time I wrote that, the window manager did not call all the neccessary functions of my custom window manager, so I had to modify the ugfx-core code. I also hacked some basic z-order functionality in. In the end it's nothing more than ordering the widgets in the lists with widgets based on this z-order. It also doesn't do anything smart at all. It just redraws the entire screen when something changes which is not really efficient. I short: What you see in that video is totally incompatible with the current uGFX, because I modifed the uGFX itself.

Hah, Ok. I'll never get over this. Im sure of it.

While working with the LTDC I stumbled up on two issues in the LTDC driver: See https://git.ugfx.io/uGFX/uGFX/src/master/drivers/gdisp/STM32LTDC/gdisp_lld_STM32LTDC.c#L60 the sync field is 8-bit, while it seems it should be 32-bit as the corresponding defines are > 8 bit. "PIXIL_POS" ( see https://git.ugfx.io/uGFX/uGFX/src/master/drivers/gdisp/STM32LTDC/gdisp_lld_STM32LTDC.c#L98 ). Why is it called PIXIL and not PIXEL? Is this on purpose or is this a mistake? The same macro ended up in gdisp_lld_fb24bpp.c and gdisp_lld_framebuffer.c

I know, I know regarding the layers. The mean reason i wanted to go for the dual frame buffer for a single layer for the "background" with the menu in a second layer, is that the "background" can be updated while the menu is shown and I didn't want it to go semi-glitchy. But maybe this isn't really an issue at all. At a decent frame rate this should be hardly noticeable (i hope). I "need" the second layer to implement some transparency/alpha channel for the menu. Maybe I should look a bit into the DMA2D a bit more, maybe I can make something useful out of that. Regarding the timings. I checked them for the SDRAM, the timings seems to be already pretty close to the fastest possible settings. Otherwise I guess the 800x480 is probably not really the most suitable display for this. It's mainly a playground anyway. I found some post from king2 on this forum, he also states 800x480 with two layers at the same time isn't going to happen. The SDRAM+F429 isn't fast enough. Time to get some F7 discovery then.

Thank you Tectu. I ported the "sliding menu" to the F429+LTDC. Seems to work OK-ish. I implemented it by using a single layer and swapping the framebuffers ( one is updated, while the other is displayed). It would be nice to use the two layer feature, but I cannot get it to work properly. As soon as I enable the second/foreground layer, I get (synchronisation??) issues. I can lower the pixel clock to "solve" this issue, but then the frame rate gets unacceptably low. All this using a STM32F429-Discovery with a 800x480 display. Any known limitations with this setup?

Hiho, I finally took some time to hook up some display to the LTDC of my STM32F429-discovery. That part works like a charm now. My goal is to get to this: https://www.youtube.com/watch?v=_1mRUhAzPoo (which is currently SDL and pixmap magic only) Anyway. I want to use multiple layers/blending/whatever to achieve the same on the display connected to the F429, but I'm not entirely sure what the current state of the LTDC in combination with two layers is in uGFX. I read this post by Tectu: https://community.ugfx.io/topic/447-support-for-stm32f469i-discovery/#comment-3637, but I'm not entirely sure if this is actually there or has to be implemented. From what I can see named functionality in gdisp_lld_control and gdisp_lld_query is yet to be implemented (by me). Also i'm not entirely sure about "adding support for multiple LTDC layers is by using the multiple displays support". What does Tectu try to say here? Do I have to make a copy of the current LTDC driver and use that as second display? Some extra pointers in the right direction would be nice.