Hi Markus,
first of all, thanks a lot for the positive feedback! :-)
In principle there are two possibilities to combine the camera image with the user interface:
1.) Using a separate hardware layer - The LTDC module is able to read two different framebuffers and to combine them together. This means, the foreground buffer contains the user interface, the background buffer contains the camera image. In order to make the camera image visible, it is necessary to place a transparent rectangle within the UI application to let the video "shine through".
The advantage of this approach: Simple solution. Each software part (camera / Embedded Wizard UI application) can update its framebuffer independently. The disadvantage of this solution: The LTDC has to read two framebuffers permanently from the SDRAM (e.g. 60 times per second), which costs a certain amount of memory bandwidth.
2.) Drawing the camera image directly into the framebuffer of the UI application.
Of course, you can overwrite the framebuffer content (backbuffer) that is previously prepared by Embedded Wizard. In case you are using the mode EW_USE_DOUBLE_BUFFER the LTDC will get an notification about the new framebuffer address directly after the graphics composition is done (see function EwSetFramebufferAddress() within the file BoardConfig.c or function EwBspSetFramebufferAddress() within the file ew_bsp_display.c). You can hook into this function and overwrite the framebuffer content.
The advantage: Simple solution, fast, efficient. The disadvantage: You have to know what you do, otherwise you will overwrite the UI content. And: You can not combine the video image with the user interface, e.g. you cannot place a button over the camera image.
3.) Usage of Views::Applet
Another possible approach is to use the class Views::Applet in order to display external decoded content within an Embedded Wizard UI application. As example please have a look into the installed example 'Applet'.
The usage of Views::Applet is recommended in cases you want to integrate an external application into the graphics composition of your Embedded Wizard UI application.
This infrastructure is a generic approach to include external content into the composition of the UI application - but this is much more work than (1) or (2).
I hope this answers your question...
Let us know the result!