When an error or warning occurs during runtime of your GUI application, the error code and additional information (known as info, info1 and info2) are output on the debug console of your target device. On most target systems, these messages are sent via serial interface to a connected terminal or console application. We strongly recommend establishing a console connection during development and debugging to monitor these error messages effectively.

This reference provides detailed descriptions of all error codes with practical guidance to help you identify and resolve issues quickly. The different error numbers for similar issues help us distinguish where problems occur within the codebase. If you have access to the source code of the Run Time Environment and Graphics Engine (available with Professional license), you can search for specific error numbers to pinpoint the exact location.

Out of memory.

The application has exhausted available memory during object creation, surface allocation, or resource loading. This typically occurs when the heap is too small, memory is fragmented, or there are memory leaks.

For guidance on memory management, see Estimating the Data Memory (RAM) usage during development, Monitoring the Data Memory (RAM) usage during runtime and especially Optimizing the Data Memory (RAM) usage. For handling out-of-memory conditions at runtime, see the function EwPanic() which can be customized according to your requirements (e.g., to initiate a system restart). For safety-critical applications, refer to Certification Aspects.

Failed to initialize the graphics subsystem in the target device.

Failed to load the global CLUT (color look up table).

Failed to initialize the Graphics Engine core functionality.

Failed to initialize the bitmap resource loader.

Failed to initialize the font resource loader.

Failed to initialize the Attributed Text sub-system.

Failed to initialize the graphics tasks sub-system.

Failed to create surface with format EW_PIXEL_FORMAT_NATIVE, width=info1, height=info2.

Failed to create surface with format EW_PIXEL_FORMAT_ALPHA8, width=info1, height=info2.

Failed to create surface with format EW_PIXEL_FORMAT_INDEX8, width=info1, height=info2.

Failed to create surface with format EW_PIXEL_FORMAT_RGB565, width=info1, height=info2.

Failed to create constant surface with format EW_PIXEL_FORMAT_NATIVE, width=info1, height=info2.

Failed to create constant surface with format EW_PIXEL_FORMAT_ALPHA8, width=info1, height=info2.

Failed to create constant surface with format EW_PIXEL_FORMAT_INDEX8, width=info1, height=info2.

Failed to create constant surface with format EW_PIXEL_FORMAT_RGB565, width=info1, height=info2.

Can't create a bitmap with format EW_PIXEL_FORMAT_SCREEN.

Failed to initialize new issue for destination bitmap info1.

Failed to load bitmap resource info1.

Failed to lock the surface info1 for direct memory access.

Failed to obtain the pixel data of a bitmap resource info1.

Failed to load the CLUT of the bitmap resource info1.

Invalid parameters to lock bitmap info1, frame number info2.

Invalid parameters to modify the palette of the bitmap info1.

Failed to load font resource info1.

The glyph cache is too small to load the glyph info2 from the font resource info1. Please increase the glyph cache size.

Invalid parameters to create viewport.

Failed to create viewport.

Invalid viewport info1 to perform screen update.

Failed to start the update of the viewport info1.

Invalid destination bitmap info1, frame number info2 in the drawing operation.

Invalid destination bitmap info1, frame number info2 in the copy bitmap operation.

Invalid source bitmap info1, frame number info2 in the copy bitmap operation.

Not convex destination polygon to warp bitmap.

Invalid destination bitmap info1, frame number info2 in the text output operation.

Invalid font info1 in the text output operation.

Invalid font info1 in text extent calculation.

Invalid parameters to get glyph metrics.

Invalid parameters to lock glyph.

Invalid parameters to get kerning information.

No free global CLUT entries to alloc user color.

Invalid global CLUT entry info1 to free user color.

Invalid global CLUT entry info1 to modify user color.

Invalid size (width=info1, height=info2) of bitmap to create.

Failed to get metrics for glyph info2 from the font info1.

This error occurs when the Graphics Engine cannot retrieve metrics for a requested character (glyph) from a font resource. The info1 parameter shows the affected font name and info2 contains the Unicode character code causing the problem.

Common causes:

The TrueType font file does not contain the requested character. This frequently affects special characters, non-Latin scripts (Greek, Cyrillic, Chinese), or control characters like tab (code 9) or space (code 32). Solution: Use a Unicode-complete font or verify the font supports the required characters.

The character exists in the font but is not included in the font resource's Ranges attribute. Solution: Add the missing Unicode range or specific character code to the Ranges attribute (e.g. 0x0400-0x04FF for Cyrillic).

Applications may try to display non-printable control characters like tabs (\t) or carriage returns (\r). Solution: Preprocess input strings to remove or replace control characters, or map them to printable characters in the Ranges attribute.

Font-specific issues where certain glyphs are not properly accessible despite being present in the font file. This can occur with some font variants or when using Bold/Italic attributes. Solution: Try different font variants, verify the font file integrity, or switch the font engine from Windows to FreeType in the FontConversion attribute.

Failed to create glyph info2 from the font info1.

Failed to load glyph info2 from the font info1.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxBeginUpdateArea() function.

The 'IssueBuffer' for destination bitmap info1 is too small for polygon data with info2 edges. Adjust in your project the macro definition EW_MAX_ISSUE_TASKS and rebuild the entire application. You can also reduce the number of edges stored in the path. If you are using one of our prepared Build Environments you can configure the macro EW_MAX_ISSUE_TASKS in the file ewconfig.h. See Target Configuration for details.

EwWarpBitmap() operation has been omitted because of the resulting destination area being wider or higher than 4096 pixel. Trying to warp bitmap for such big area will lead to integer arithmetic overflows.

To use EwEnableGfxTaskTracing() you have to rebuild Graphics Engine with the define EW_SUPPORT_GFX_TASK_TRACING. Otherwise the function has no effect.

The support for operations to fill and stroke paths is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_PATH_FUNCTIONS. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

The support for operations to scale, rotate or warp bitmaps is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_WARP_FUNCTIONS. This error can also occur when your application uses the Line view to display a line with thickness greater than 1 pixel. In such case the line is rendered using the warp functionality. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

The support for operations involving EW_PIXEL_FORMAT_INDEX8 bitmaps is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_INDEX8_SURFACES. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

The support for operations involving EW_PIXEL_FORMAT_RGB565 bitmaps is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_RGB565_SURFACES. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

No font (NULL) in text extent calculation.

The support for bi-directional text is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_BIDI_FUNCTIONS. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstNativeSurface() function. This error can occur when your Embedded Wizard project is configured to generate bitmap resources in the DirectAccess format. Please verify the attribute ModeOfBitmapResources in your Embedded Wizard project. You can also try to clean/rebuild your project.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstAlpha8Surface() function. This error can occur when your Embedded Wizard project is configured to generate bitmap resources in the DirectAccess format. Please verify the attribute ModeOfBitmapResources in your Embedded Wizard project. You can also try to clean/rebuild your project.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstIndex8Surface() function. This error can occur when your Embedded Wizard project is configured to generate bitmap resources in the DirectAccess format. Please verify the attribute ModeOfBitmapResources in your Embedded Wizard project. You can also try to clean/rebuild your project.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstRGB565Surface() function. This error can occur when your Embedded Wizard project is configured to generate bitmap resources in the DirectAccess format. Please verify the attribute ModeOfBitmapResources in your Embedded Wizard project. You can also try to clean/rebuild your project.

Trying to open an invalid font resource.

Trying to open an invalid font resource info1.

The font info is not available. Ensure, that the font is installed and registered properly. On the target system use the function EwRegisterFont(). For prototyping, install the font file in the Windows font directory.

Wrong Bitmap Loader and Software Pixel Driver combination. The color formats differ.

The bitmap resource has not the expected format.

The bitmap resource info has not the expected format. Please verify the attribute PlatformPackage in your Embedded Wizard project. It should correspond to the color format of your target system. You can also try to clean/rebuild your project.

The rotation of the bitmap resource info doesn't correspond to the configuration the Graphics Engine has been built for.

Please verify whether the attribute ScreenOrientation in your Embedded Wizard project does correctly conform the value of the define EW_SURFACE_ROTATION used during the build process. This define is typically set automatically based on the project's orientation configuration, but may need to be defined manually in custom makefiles or project files (e.g., -DEW_SURFACE_ROTATION=90). Verify that the EW_SURFACE_ROTATION value matches your project's ScreenOrientation attribute.

The bitmap resource info is stored with wrong color format. Please verify whether the attributes ColorPremultipliedAlpha and ColorChannelsOrder in your Embedded Wizard project do correctly conform the values of the defines EW_COLOR_CHANNEL_BIT_OFFSET_RED, EW_COLOR_CHANNEL_BIT_OFFSET_GREEN, EW_COLOR_CHANNEL_BIT_OFFSET_BLUE, EW_COLOR_CHANNEL_BIT_OFFSET_ALPHA and EW_PREMULTIPLY_COLOR_CHANNELS. These defines are architecture specific and color specific. Usually these settings are predefined for your target system (typically in ewextgfx.h). Verify that your project's color format attributes match your platform's color channel configuration. You can also try to clean/rebuild your project.

The RGB565 bitmap resource info is stored with wrong color format. Please verify whether the attribute ColorChannelsOrderOfRGB565 in your Embedded Wizard project does correspond to the values of the defines EW_RGB565_COLOR_CHANNEL_BIT_OFFSET_RED, EW_RGB565_COLOR_CHANNEL_BIT_OFFSET_GREEN and EW_RGB565_COLOR_CHANNEL_BIT_OFFSET_BLUE. These defines are architecture specific and color specific. Usually these settings are predefined for your target system (typically in ewextgfx.h). Verify that your project's color format attributes match your platform's color channel configuration. You can also try to clean/rebuild your project.

The bitmap resource has not the expected format.

The bitmap resource info has not the expected format. Please verify the attribute PlatformPackage in your Embedded Wizard project. It should correspond to the color format of your target system. You can also try to clean/rebuild your project.

Wrong Bitmap Loader and Software Pixel Driver combination. Color format differ.

The image file info is not available or the format of the image file is not supported by the extern loader. Ensure, that a valid file is available on the target system.

Trying to load an invalid bitmap resource info1.

Wrong Viewport Interface and Pixel Driver combination.

Calling twice the function EwRegisterFlashAreaReader() with different flash start/end addresses.

Not convex destination polygon to warp bitmap. One of the W parameters is 0 (zero).

Timer info1 not in the timers list.

String index out of the string length.

Trying to modify a constant string.

Trying to release a string with usage counter 0.

Maximum value for a string usage counter (65535) reached.

postsignal is failed. The signal is just delivered.

This error occurs when attempting to post a signal that is already being processed, which could lead to endless signal delivery. The system automatically detects and suppresses such recursive postsignal operations to prevent infinite loops. Starting with version 13, this error is only reported after more than 3 repeated attempts.

Common causes:

Recursive postsignal calls: A slot method triggered by postsignal attempts to post the same signal again while it's still being processed. This creates direct recursion that could result in infinite signal delivery. Solution: Review the slot method implementation to avoid posting the same signal recursively, or use conditional logic to break the cycle.

Debugging: This issue is best debugged in the Prototyper where you can trace the signal flow and identify the recursive pattern. Use the Prototyper to reproduce and analyze the signal chain causing the recursion.

No class (NULL).

Object info1 is not in the root set.

The specified class parameter to create a new instance is not a valid class.

Recursive access to an autoobject info1 performing the initialization.

Trying to use the function EwSetStackBaseAddress() with Runtime Environment not configured to run Immediate Garbage Collection. Operation is ignored.

No CPU stack information available to start the Immediate Garbage Collection. Please call the function EwSetStackBaseAddress() at the initialization time of the application to provide to the Runtime Environment the base address of the CPU stack. Immediate Garbage Collection is not started.

New Garbage Collection started while the actual Garbage Collection is not yet finished. Recursive Garbage Collections are not permitted. Operation is ignored.

Try to use the function EwModifyBitmapPalette() to modify the palette of loaded originally from a resource. Such bitmaps and their associated palettes are considered as immutable. Operation is ignored. info1 contains the address of the respective bitmap.

Bitmap is corrupted. This error should usually never occur unless the data structure of the bitmap has not been initialized correctly or it has been overwritten. info1 contains the address of the respective bitmap and info2 contains the number of the frame addressed in actual operation.

Failed to map a bitmap frame in the function EwModifyBitmapPalette().

Failed to map a bitmap frame in the function EwCreateBitmap().

Failed to map a bitmap frame during loading of a bitmap resource info1.

Trying to use EwAllocHeapBlock() without initializing the Heap Manager. Use EwInitHeap() and EwAddHeapMemoryPool() first.

Trying to use EwFreeHeapBlock() with an invalid memory block address or the internal heap management structures are corrupted. In the last case you can use the function EwVerifyHeap() to check the heap for its coherence.

The memory area specified in the function call EwAddHeapMemoryPool() is too small to be added to the memory pool of the Heap Manager. The operation is ignored.

The function EwVerifyHeap() has detected an incoherence in internal Heap Management structures. info1 specifies the address of the affected memory area within the memory pool (see function EwAddHeapMemoryPool()).

This error indicates memory corruption within the heap management system and is a critical issue that requires immediate attention. The heap management structures have been damaged, which can lead to unpredictable application behavior and crashes. This error is automatically detected as EwVerifyHeap() is called in each main loop cycle (see Main Loop). The info2 value indicates which specific coherence test failed, helping to narrow down the type of corruption.

Common causes:

SDRAM hardware issues: Incorrectly configured SDRAM timing, refresh rates, or faulty memory hardware can cause random memory corruption. This is the most common cause on custom hardware. Solution: Verify SDRAM configuration according to datasheet specifications and run comprehensive memory tests to ensure hardware stability. For comprehensive guidance on SDRAM configuration and testing during custom hardware integration, see Verify Memory Subsystem.

Multithreading violations: Accessing the Embedded Wizard GUI application from multiple threads simultaneously can corrupt memory structures. The entire GUI application must run in a single GUI thread context. Solution: Ensure all Embedded Wizard operations occur only in the GUI thread. Use worker threads only for background tasks and communicate with the GUI thread through proper synchronization mechanisms. See Take care in multi-threading environments. Use EwInvoke() and EwInvokeCopy() to safely pass data and function calls from worker threads to the GUI thread.

Memory overwrites: Direct memory corruption caused by buffer overflows, incorrect pointer arithmetic, or improper memory access in native code. This commonly occurs when implementing Extern Bitmap interfaces or incorrectly handling strings within native code. Solution: Review all native code for proper bounds checking and memory access patterns.

Stack overflow: Insufficient stack size or excessive recursion in native code implementations can cause stack corruption that affects heap structures. Solution: Increase stack size for the GUI thread or optimize native code functions and local variable usage.

Hardware-related issues: Unstable power supply, electromagnetic interference, or temperature-related problems can cause random memory corruption. Solution: Verify hardware stability and environmental conditions. For SDRAM-related issues, implement comprehensive memory tests before initializing the Embedded Wizard application.

Trying to perform a drawing operation within a bitmap loaded originally from a resource. Such bitmaps are considered as immutable. Operation is ignored. info1 contains the address of the respective bitmap. info2 contains the specified frame number.

Missing metric information in TrueType font file. The external TrueType font engine was not able to find the tables OS/2 nor hhea within the font file. info contains the name of the affected font. The tables are required to estimate the correct font size.

Drawing into a Native bitmap but the support for Native surfaces as drawing destination is disabled in the Graphics Engine (the Graphics Engine is compiled with the C macro EW_DONT_USE_NATIVE_SURFACES_AS_DESTINATION). In such case the operation to draw into a Native bitmap has no effect. info1 contains the address of the affected Native bitmap and info2 the frame number within the bitmap. If you are using one of our prepared Build Environments you can configure the macro EW_DONT_USE_NATIVE_SURFACES_AS_DESTINATION in the file ewconfig.h. See Target Configuration for details.

Printing rotated text (Orientation other than Normal) but the support for Warp operations (texture mapping operations) is disabled in the Graphics Engine (the Graphics Engine is compiled with the C macro EW_DONT_USE_WARP_FUNCTIONS). In such case the operation to draw the text has no effect. If you are using one of our prepared Build Environments you can configure the macro EW_DONT_USE_WARP_FUNCTIONS in the file ewconfig.h. See Target Configuration for details.

Performing a drawing operation with color or opacity gradient but the support for gradients is disabled in the Graphics Engine (the Graphics Engine is compiled with the C macro EW_DONT_USE_GRADIENTS). In such case the operation to draw with color or opacity gradient has no effect. If you are using one of our prepared Build Environments you can configure the macro EW_DONT_USE_GRADIENTS in the file ewconfig.h. See Target Configuration for details.

Trying to create a Native bitmap but the support for Native bitmaps is disabled in the Graphics Engine (the Graphics Engine is compiled with the both C macros EW_DONT_USE_NATIVE_SURFACES_AS_DESTINATION and EW_DONT_USE_NATIVE_SURFACES). In such case no bitmap is created. If you are using one of our prepared Build Environments you can configure the macros in the file ewconfig.h. See Target Configuration for details.

Trying to load a Native bitmap resource but the support for Native bitmaps is disabled in the Graphics Engine (the Graphics Engine is compiled with the C macro EW_DONT_USE_NATIVE_SURFACES). In such case no bitmap resource is loaded. If you are using one of our prepared Build Environments you can configure the macro in the file ewconfig.h. See Target Configuration for details.

Trying to load a string constant stored in compressed format but the support for string decompression is disabled in the Runtime Environment (the Runtime Environment is compiled with the C macro EW_DONT_USE_COMPRESSION). In such case the string load operation fails resulting in an empty string. If you are using one of our prepared Build Environments you can configure the macro in the file ewconfig.h. See Target Configuration for details.

Trying to load a bitmap resource stored in compressed format but the support for bitmap decompression is disabled in the Runtime Environment (the Runtime Environment is compiled with the C macro EW_DONT_USE_COMPRESSION). In such case no bitmap resource is loaded. info1 contains the pointer to the affected bitmap resource. If you are using one of our prepared Build Environments you can configure the macro in the file ewconfig.h. See Target Configuration for details.

This error is reported when the application runs out the CPU stack or the code is executed in context of a foreign thread. Please ensure to invoke Embedded Wizard related code always in context of the GUI thread. See also Take care in multi-threading environments. If the multi threading is not the cause of this error, your CPU stack is possibly too small. Enlarge it.

This error indicates that either the GUI thread has exceeded its stack boundaries or Embedded Wizard functions are being called from a different thread/task context. The detection mechanism relies on stack address monitoring when EwSetStackAddressArea() is properly configured.

Common causes:

Stack overflow in GUI thread: The main GUI thread has consumed more stack space than allocated, typically due to deep function call chains, large local variables, or excessive recursion in native code. Solution: Increase the stack size using EW_GUI_THREAD_STACK_SIZE in ewconfig.h or optimize native code to reduce stack usage.

Wrong thread context: Embedded Wizard functions are being called from worker threads, interrupt service routines, or other non-GUI contexts. The system detects this by comparing the current stack pointer against the registered GUI thread stack area. Solution: Ensure all Embedded Wizard operations occur only in the GUI thread. Use EwInvoke() and EwInvokeCopy() to safely pass data and function calls from worker threads to the GUI thread.

Missing stack configuration: The function EwSetStackAddressArea() has not been called or is configured incorrectly, preventing proper stack boundary detection. Solution: Call EwSetStackAddressArea() during GUI thread initialization with correct base and end addresses.

Immediate garbage collection issues: When EW_USE_IMMEDIATE_GARBAGE_COLLECTION is enabled, the garbage collector needs accurate stack information to scan for object references. Incorrect stack configuration can trigger false positives. Solution: Verify stack address calculation and ensure EW_USE_IMMEDIATE_GARBAGE_COLLECTION is properly configured.

OS-specific stack allocation: In multi-threaded environments, operating systems may allocate thread stacks dynamically, requiring runtime stack address queries. Solution: Use OS-specific functions to determine the actual thread stack boundaries and pass them to EwSetStackAddressArea().

Configuration example for MCU: In embedded systems, the GUI thread typically calculates its stack area during initialization:

Stack size configuration: The macro EW_GUI_THREAD_STACK_SIZE in ewconfig.h defines the allocated stack size. Typical values range from 8KB for simple applications to 32KB or more for complex applications with deep call stacks. Monitor actual stack usage during development to determine optimal sizing.

Failed to create a wrapped surface.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstNativeSurfaceWrapped() function.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstAlpha8SurfaceWrapped() function.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstIndex8SurfaceWrapped() function.

Incomplete interface to the underlying graphical subsystem. Missing the implementation of the EwGfxCreateConstRGB565SurfaceWrapped() function.

Invalid destination bitmap info1, frame number info2 in the bitmap filter operation.

Invalid source bitmap info1, frame number info2 in the bitmap filter operation. Please note, filter operations are restricted to single-frame bitmaps only.

Invalid mask bitmap info1 in the bitmap filter operation. Expected is a bitmap in format ALPHA8 containing exact 1 frame only. Multi-frame bitmaps are not supported by the bitmap filter operation.

Failed to initialize new issue for destination bitmap info1.

The support for operations to mask, tint or blur bitmaps is not available because the Graphics Engine is compiled with the following three macros being defined: EW_DONT_USE_BLUR_FUNCTIONS, EW_DONT_USE_MASK_FUNCTIONS and EW_DONT_USE_TINT_FUNCTIONS. If you are using one of our prepared Build Environments you can configure the macros in the file ewconfig.h. See Target Configuration for details.

The support for operations to blur bitmaps is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_BLUR_FUNCTIONS. If you are using one of our prepared Build Environments you can configure the macro in the file ewconfig.h. See Target Configuration for details.

The support for operations to mask bitmaps is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_MASK_FUNCTIONS. If you are using one of our prepared Build Environments you can configure the macro in the file ewconfig.h. See Target Configuration for details.

The support for operations to tint bitmaps is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_TINT_FUNCTIONS. If you are using one of our prepared Build Environments you can configure the macro in the file ewconfig.h. See Target Configuration for details.

Could not create a temporary surface needed to store intermediate contents when performing a blur bitmap operation.

The support for blur operations is restricted for target systems using the format RGB565, RGB888 or RGBA8888 for the frame buffer. In your application case other frame buffer format is used. The color space in such case is too small for the fine gradients resulting from the blur effect.

Unexpected race condition detected when using the function EwInvoke() or EwInvokeCopy(). This error indicates that the low-level Runtime Environment function EwAtomicFetchAndAdd() has not been adapted properly on your target system.

Trying to use the function EwInvoke() or EwInvokeCopy() but there is no invocation queue configured. See the function EwInitInvocations().

The amount of data to copy to the invocation queue passed to the function EwInvokeCopy() is larger than the queue itself. It will never fit inside the queue even if the queue were empty.

This error occurs when the data payload exceeds the total capacity of the invocation queue, which is used to safely pass data from worker threads to the GUI thread. The queue size is defined by EW_INVOCATION_QUEUE_SIZE in ewconfig.h.

Common causes:

Data payload too large: The data being passed to EwInvokeCopy() exceeds the total queue capacity. This commonly occurs with large strings or data structures. Solution: Segment large data into smaller chunks that fit within the queue capacity, or use EwInvoke() with persistent data storage instead of copying large payloads.

Insufficient queue configuration: The EW_INVOCATION_QUEUE_SIZE is too small for the application's needs. Default size may not accommodate larger data transfers. Solution: Increase EW_INVOCATION_QUEUE_SIZE in ewconfig.h and rebuild the application. Consider memory constraints when sizing.

Failed to create an ALPHA8 surface to store blurred contents of a vector graphic object. See preceding error messages. Possibly there is not sufficient memory available to create the surface.

Failed to lock the ALPHA8 surface info1 for direct memory access. The surface is used as source in a blur operation.

Failed to create an ALPHA8 surface needed to store intermediate results of a blur operation. See preceding error messages. Possibly there is not sufficient memory available to create the surface.

Trying to display a rounded rectangle, rounded border or rounded rectangular shadow. This operation requires vector graphic functionality. The support for operations to fill and stroke paths is however not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_PATH_FUNCTIONS. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

Trying to render an ALPHA8 bitmap with blurred content of a vector graphic shape. This function requires vector graphic functionality. The support for operations to fill and stroke paths is however not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_PATH_FUNCTIONS. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

Failed to initialize the SVG resource loader.

Failed to load SVG resource info1.

The SVG resource has not the expected format.

Failed to initialize the SVG sub-system.

The support for operations to read and parse SVG images at the runtime is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_SVG_READER. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

The support for operations to render SVG images is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_SVG_FUNCTIONS. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

The support for operations to render komplex linear or radial gradients is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_GRADIENTS or EW_DONT_USE_PATH_FUNCTIONS. If you are using one of our prepared Build Environments you can configure this macros in the file ewconfig.h. See Target Configuration for details.

Invalid destination bitmap info1, frame number info2 in the drawing operation.

Drawing into a Native bitmap but the support for Native surfaces as drawing destination is disabled in the Graphics Engine (the Graphics Engine is compiled with the C macro EW_DONT_USE_NATIVE_SURFACES_AS_DESTINATION). In such case the operation to draw into a Native bitmap has no effect. info1 contains the address of the affected Native bitmap and info2 the frame number within the bitmap. If you are using one of our prepared Build Environments you can configure the macro EW_DONT_USE_NATIVE_SURFACES_AS_DESTINATION in the file ewconfig.h. See Target Configuration for details.

Trying to perform a drawing operation within a bitmap loaded originally from a resource. Such bitmaps are considered as immutable. Operation is ignored. info1 contains the address of the respective bitmap. info2 contains the specified frame number.

Failed to initialize new issue for destination bitmap info1.

The 'IssueBuffer' for destination bitmap info1 is too small for polygon data with info2 edges. Adjust in your project the macro definition EW_MAX_ISSUE_TASKS and rebuild the entire application. You can also reduce the number of edges stored in the path. If you are using one of our prepared Build Environments you can configure the macro EW_MAX_ISSUE_TASKS in the file ewconfig.h. See Target Configuration for details.

Invalid memory area specified in parameter of EwSetBlobData(). Also, the memory area has to begin at a modulo 4 byte address.

Incompatible byte order. The target system is using the big-endian. Blob file content is little-endian.

Invalid Blob file content.

The version of the Blob file does not correspond to the version of the Runtime Environment. The Blob file was generated for an older or newer version.

The Blob file is not correctly linked to the binary. See also Find and prepare the Blob file.

The requested resource (unit id: info1, member id: info2) is not available in the Blob file. See also the blob_names.txt file to map the ids in real project names.

The Blob file entity (unit id: info1, member id: info2) is not a resource. See also the blob_names.txt file to map the ids in real project names.

The requested constant (unit id: info1, member id: info2) is not available in the Blob file. See also the blob_names.txt file to map the ids in real project names.

The Blob file entity (unit id: info1, member id: info2) is not a constant or it is a constant with data type not corresponding to the type in the binary. See also the blob_names.txt file to map the ids in real project names.

The support for Blob files is not available because the Runtime Environment is compiled without a defined macro EW_USE_BLOB_DATA. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

Invalid font resource format.

The support for runtime rasterized vector fonts is not available because the Graphics Engine is compiled with defined macro EW_DONT_USE_PATH_FUNCTIONS. If you are using one of our prepared Build Environments you can configure this macro in the file ewconfig.h. See Target Configuration for details.

Overflow in buffer storing vector information for path drawing functions. Assuming the CPU is calculating correctly, this error should never occur.

#651

Trying to release too much memory from internal issue buffer.

Trying to print blurred text. The support for operations to blur operations is not available because the Graphics Engine is compiled with the defined macro EW_DONT_USE_BLUR_FUNCTIONS. If you are using one of our prepared Build Environments you can configure the macro in the file ewconfig.h. See Target Configuration for details.

Out of memory while trying to print blurred text. No sufficient memory to store blurred glyphs.

Failed to lock bitmaps containing blurred glyphs while trying to print blurred text.

The glyph cache is too small to load the glyph info2 from the font resource info1. Please increase the glyph cache size. The error was reported while trying to display blurred text.

Failed to load glyph info2 from the font info1. The error was reported while trying to display blurred text.