Skip to main content
brianshankland9
Associate III
March 12, 2019
Question

Help with an internal assert failure

  • March 12, 2019
  • 8 replies
  • 1831 views

I'm getting what looks like assert failures while running a TouchGFX project in Visual Studio.

Its happening on two of my designed screens out of 12 so its likely something I've created but need a hint of where to look for the fault.

It happens as soon as the page is switched to so part of its initial draw.

In case the image is too small the assert looks to be raised while performing a TestArea draw:

ucrtbased.dll!_wassert(const wchar_t * expression, const wchar_t * file_name, unsigned int line_number) Line 404 C++

Any clues to which property combination I may have set incorrectly in the Designer much appreciated.

The only changes made to the gui generated files have been to *** in missing #includes for widget buttons, and this has been working for all other screens.

This topic has been closed for replies.

8 replies

Martin KJELDSEN
Principal III
March 13, 2019

The assert in LCD::drawStringInternal() is

assert(false && "Unknown character used in wildcard string. Make sure that all used characters are included in the texts.xlsx file. Read the text database section in the documentation for more information.");

Are you trying to render a TextArea with wildcards?

/Martin

brianshankland9
Associate III
March 13, 2019
Hi Martin, Yes, most of my text areas are wildcards, only a few common headers are ResourcIDs Could this be related to the font error I’ve already raised when it reports I’m missing characters although they are all defined as wildcards? I thought if a character was missing it would use the Fallback Character “?�? I’ve seen this in action on my earlier projects before I added in wildcard ranges. All my fonts have fallbacks set (this is the same project as the one I dropboxed to you earlier) the failing screen is NetworkSetup2 I now have seen a debug window is being shown (hidden behind app) It has the message “WARNING: Skipping character ‘p’ (Unicode 0x0070=112)“ for one of my screens and also “WARNING: Skipping character 'Ã' (unicode 0x00C7=199)�? for the other. regards _________________________________________________­_ Brian Shankland Icon Research Ltd 3 Raw Holdings | East Calder | West Lothian | EH53 0HY | UK T: +44 1506 885000 Ext 226 F: +44 1506 885501 www.iconresearch.co.uk<>