BRT Community

The file Esd_Context.c in function Esd_Render(Esd_Context *ec)
has code lines in DEBUG builds:
  #if defined(_DEBUG)
   // This will cause a dark red screen in case background video incorrectly swaps the display
   EVE_Hal_startTransfer(phost, EVE_TRANSFER_WRITE, RAM_DL);
   EVE_Hal_transfer32(phost, CLEAR_COLOR_RGB(0x40, 0x00, 0x20));
   EVE_Hal_transfer32(phost, CLEAR(1, 1, 1));

looks a bit suspect to me. IMHO this should be an opt-in sequence in request, not the default for debug.

@Kaetemi, thanks for your answer,
Yes, the Idle function callback of the application could be used
for some cases, BUT it is called somewhat  'unpredictable' or multiple times.
  (see Esd_Loop()  =>  Esd_Update() : Idle at least once every frame)

I STRONGLY propose to add a specific app-callback,
I guess best place would be here in Esd_Loop as last line in the while-loop, like:
ESD_CORE_EXPORT void Esd_Loop(Esd_Context *ec)
{
........Esd_Start(ec);
   while (Esd_IsRunning__ESD() && !ec->RequestStop)
   {
      Esd_Update(ec);
      Esd_Render(ec);
      Esd_WaitSwap(ec);
                ec->FrameDone();  // <<<<< CALLBACK APP (ONLY HERE!)
   }
   Esd_Stop(ec);
}

Thanks!

* In contradiction to the EVE concept of a co-processor for offloading host MCU from graphics drawing,
   the ESD generated source has an endless, fulltime burner loop for repeated Updates/Render (about each 5-20ms), even if the HMI didn't change!!??
   What is the rational behind this?
   Any chance for changing (in near future) to an event-driven (dirty-state => refresh) model?
   Also note:
     - what about the touch-input tags repeatedly getting swapped out+in?
     - RTOS unfriendly.
     - this is energy-unfriendly if battery powered.
     - causes constant EMI on cables.

* the new 'Switch Page' concept is very under-documented! (e.g. hierarchical usage),
    there is a 'Fill Display' show on a screenshot (Figure 44, PDF man 4.15), but undocumented!
     Urgent need for new tutorial video explaining all this, sample page transition.

* There is a well hidden document BRT_AN_073 for porting ESD source to STM32L4.
   Bad: the listed files are not available from bridgetek github anywhere, namely EVE_HalImpl_STM32L476GDISCOVERY.c !!??
      (by pure chance I found an older 'clone' at https://github.com/kaetemi/nuklear_eve )

* please add an option to export (eclipse) source with alternative name for the entry fn, instead of main().

Thanks!