Search Results

Just asking a few hypothetical questions about using GUI_Exec() or GUI_Exec1() calls because I sometimes experience HardFaults when GUI_Exec() was called. The below snippet is from emWin Manual (section 6.1.8.7.1): Source Code (12 lines) If WM_CreateWindow() and WM_CreateTimer() and others like GUI_FillRectEx() and GUI_DrawGradientV() were called 1000 times prior to next GUI_Exec() call will the job queues get compromised (overflow) or does that depend on my program settings like heap size or so…

I am in the process of setting up emWin to run AppWizard project on a custom board target (custom bsp) with NXP MK22FX512AVLQ12 MCU. There appears to be a library call "APPW_Init()" that is found in APPMainTask.c for most BSP examples that use emWin 6.10f along with AppWizard: C Source Code (15 lines)Is the APPW_Init() call needed when compiling code in my custom board target project? What happens if APPW_Init() is commented out (or not used)? Not exactly sure, but what files from "APPW_PROJECT_…

I am currently using emWin 6.10 over NXP's K22 MCU. Has anyone compiled emWin 6.10 library (emWin_M4F.a) with an IAR EWARM 7.80.4 project and got "Warning[Lt009]: Inconsistent wchar_t"? Is this linker error a real issue? Or should this warning be generally ignored? Next, what emWin version(s) are compatible with IAR EWARM 7.80.4? (i.e. compatible or built with IAR EWARM v.7.80.4 or similar version that uses wchar_t size of 2 bytes) In most cases I have to use the below linker statement in my pro…