GUI_CopyRect is not working in STemWin (STM32F7)

Christos · Oct 28th 2015, 11:27am

Hi,

Used the STemWin with quite a few demos on STM32F746G-Discovery so far succesfully, yet it seems that the GUI_CopyRect is not working.

Tested it with many code variations but no rectangle nomatter small or large, overlapping or not, could be copied.

This code supposedly copies the "Hello world!" phrase on STemWin hello world example application but it is not doing anything at all..

Source Code

void MainTask(void) {
int i,j;
GUI_Clear();
GUI_SetFont(&GUI_Font20_1);
GUI_DispStringAt("Hello world!", (LCD_GetXSize()-100)/2, (LCD_GetYSize()-20)/2);
// GUI_CopyRect here should copy the phrase 50 pixels below, yet it does nothing
GUI_CopyRect((LCD_GetXSize()-100)/2, (LCD_GetYSize()-20)/2,
(LCD_GetXSize()-100)/2, 50 + (LCD_GetYSize()-20)/2, 100, 20);
while(1);
}

Display All

Can someone tell me how can we make the GUI_CopyRect work properly?

Regards,
Christos

SEGGER - Jörg · Oct 29th 2015, 9:40am

Hi,

May there is a custom function for the copy operation is set in the configuration file LCDConf.c and may that function does not work:

LCD_SetDevFunc(i, LCD_DEVFUNC_COPYRECT, (void(*)(void))pfCustomFunction);

You could comment out that function call to check if that is the cause.

Regards, Jörg

Christos · Oct 29th 2015, 5:50pm

Hi Jörg and thanks,

Yes, that did made it to show up.
Though, as I've seen around the sources, there are a few CUSTOM_* functions (4 I think) that take advantage of the DMA2D controller and make things faster.
By commenting out the CUSTOM_CopyRect, I guess a plain memcpy happens at the standard implementation, thus its way too slow for my application.
Is there something we can do about this?

Regards,
Christos

SEGGER - Jörg · Nov 5th 2015, 9:59am

Hi Christos,

If the default behavior is too slow you can use your own function for that operation. With other words the already existing function in your configuration file (which obviously currently does not work right) should be used for that operation. In that case you should find the cause of the currently existing problem in your custom function.

Regards, Jörg

Source Code

Share