Search Results
Search results 1-11 of 11.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi Sven thanks for your support. it looks a great ideal using Window Manager to split the screen into different parts. You are using a STM32F469, are you also using the internal LCD controller? --> yes, I am using internal LCD controller. Is that possible using GUI_MEMDEV_DrawAuto() on window's WM_PAINT event? could you please also release a simple code ? At first, I used one auto device for whole screen, in my imagination, it will redraw the dirty area at different block only. but if the dirty …
-
Additional: Platoform: stm32F469 external SDRAM : 8M bytes if two GUI_AUTODEV dirty area has cover area, is that possible cause any problem? __________________ | | | A | | ________ | | | | | | | B | | | |________| | |________________| Just like above picture, dirty area A cover dirty area B, could I create two GUI_AUTODEV to draw the area in separate? why I do it.. because I want to reduce the dirty area in the smallest to speed up. Br, Titan.Chen
-
Hi on my project, I create 7 GUI_AUTODEV to draw separate dirty area to speed up screen refresh rate. But I always got hardfault_handler exception after free running for a while. check the call stack, the last function before HardFault_Handler always is emWin library function, just like _GetPixelIndex(). I have already alloc 0x400000 bytes size on external SDRAM for GUI library, I think it could not caused by memory not enough. I always try to increase stack an heap size to 0x800 and 0x400, but …
-
Hi Adrian after calling GUI_MEMDEV_DrawAuto() and then EmWin callback to callback function that specify on GUI_MEMDEV_DrawAuto. The parameter AutoDevInfo.DrawFixed, it seems only the first time callback will set to true, am I right? The time I want to discuss is, if create a bigger MEMDEV size, does EmWin core need more time to check where the dirty area ? thanks. BR, Titan.Chen
-
Hi when I execute GUI_MEMDEV_DrawAuto(), will MEMDEV create size affect EmWin process time from execute GUI_MEMDEV_DrawAuto() to really write to a display buffer? on my imagination, I think emwin core would allocate three memory buffer the same to MEMDEV_Create size. First only background picture, second is background picture + motion picture (like needle), and third also background picture + next motion picture. every time have a new motion picture draw, first memory will compare to second to d…
-
Hi Adrian simulation : // Define the available number of bytes available for the GUI // #define GUI_NUMBYTES 0x400000 // // Define the average block size // #define GUI_BLOCKSIZE 0x80 arm target: #define GUI_NUMBYTES (1024 * 1500) simulation define 4Mbytes memory pool for emwin library, only 1.5Mbyte on my ARM target system. yes I know that drawing only happen whith the callback function. In Main function, there is a while loop always set value to SPEEDOMETER widget to redraw. And invalidated wi…
-
Hi Adrian I am not talking about "why the performance is good on an ARM system", I want to know why a widget that create by Memory Device can't display on x86 evaluation SeggerEval_WIN32_MSVC_MinGW_GUI_V528 but ARM base on stm32f429 freeRTOS. I know the Speedometer demo was created using Memory Devices only, so I copy the Speedometer demo relative drawing and MEMDEV create function to my Customer Widget source code. Just like the second picture I pasted, the speedometer display success without f…
-
Hi Adrian thanks for your reply. In the customer widget document, it doesn't said widget can't implemented by Memory Device component. the SPEEDOMETER widget that create by Memory Device I test on the ARM base system , the drawing function was working well. could you please let me know why the widget works well on ARM base system? or "widgets can not be created by Memory Devices" was mean can't run on x86 evaluation SeggerEval_WIN32_MSVC_MinGW_GUI_V528 library? thanks. BR, Titan
-
Hi no any SEGGER member can help to answer the question ? BR, Titan
-
Hi I create two new widget and bind into dialog windows by function GUI_CreateDialogBox the two widget is a level meter and speedometer that drawing source code comes from "emwin-samples". level meter was capture from "Amplifier" sample and speedometer was capture from "SPEEDOMETER" I can display the level meter on SeggerEval_WIN32_MSVC_MinGW_GUI_V528 by GUI_CreateDialogBox but SPEEDOMETER that create by MEMDEV. I can see the SPEEDOMETER sometimes draw on the dialog and disappear on next tick. f…