the error code 180 indicates that your application tries to display a string containing the character with code 32 and there is no glyph in the given font for such character. To solve the problem you have to add the code 32 to the Ranges attribute of the affected font.
Important question in this context is thus which font is affected? The error message identifies the problematic font in the value info1. Actually (version <= 9.30) it shows the memory address where the font data is stored. As such it does not help a lot. What can you do?
Option 1: Review the Ranges attribute of all fonts existing in your project. Is there a font missing the code 32? Then adapt it accordingly.
Option 2: You can send us your project via e-mail and we will evaluate it with the Embedded Wizard version we are working on actually. This version displays in error 180 directly the name of the affected font instead of its address and helps so to find the problematic font member. Please provide instructions how to provoke the error.
it sounds strange. According to your description, the Ranges attribute has been changed. Or, there are some dynamic text contents in your application which sometimes involve character codes not listed in Ranges attribute. Are you sure the conversion XML to EWU is correct? I hope you can reproduce the behaviour again.
Ask Embedded Wizard
Welcome to the question and answer site for Embedded Wizard users and UI developers.
Ask your question and receive answers from the Embedded Wizard support team or from other members of the community!