Hello Earl Orlando,
I am using the D4D eGui Library with KDS 3.0 for a K20 project.
I found the same solution as yours, changing the D4D_TCHAR from unsigned short to unsigned int, as GDB assumes the wide-chars as 4-bytes characters (such as in Linux environment; Windows, instead, considers the L"...." strings as 2-bytes per character strings).
Have you any suggestion for converting UTF8 strings (received from a communication) to the correct UNICODE format for eGui? Actually I just copy the 1-byte per char UTF8 string to a 4-bytes per character D4D_TCHAR, but when it finds a 2-bytes character in the UTF-8 string, it is not correctly displayed (lowercase accented 'a' becomes a uppercase 'A' with tilde). Only 1-byte characters are correctly displayed.
I used the Freescale Embedded Gui Converter utility to create the font choosing Unicode-16bit encoding and including the Latin and 2 Latin-extended Unicode ranges.
Thanks in advance for any suggestion.
Vittorio