WinCEGeräteSE_Handbuch_Programmierung_v3.00_EN
17 / 65
3.4 Notes, recommendations, advice
3.4.1 General
The kernels of Windows CE differ significantly from those of Desktop-Windows operating systems. The
functionalities differ, many functions are missing, react differently or are only partly installed.
This is particularly worth remembering when calculating the time and effort involved.
3.4.2 Unicode is standard
Under Windows CE, function parameters are defined as Unicode (two bytes) in the Win32 API. This also
applies to standard text characters. The well-known ANSI string functions are (usually) not added directly;
wide char alternatives are used instead.
Examples:
CHAR
WCHAR
strcpy
wcscpy
A compiler-dependent alternative is to use functions with the prefix _t. Example: _tcscpy, TCHAR
(depending on the platform, this is replaced with ANSI or Unicode).
A range of conversion functions are also available between Unicode and ANSI:
Function
Description
wcstombs()
Converts wide character string into multibyte string.
mbstowcs()
Converts multibyte string into wide character string.
WideCharToMultiByte() Converts wide character string into multibyte string.
MultiByteToWideChar() Converts multibyte string into wide character string.
Table 4 – Unicode conversion
Note
In theory, the emulator is a useful tool to develop and test a program. However in
practice, this is only partly the case as the emulator does not store the hardware
and peripherals of the target devices. One example here includes the integrated
scanner on mobile devices.
ACD recommends explicitly programming the target devices (ARMV4I) and
testing the software by remote debugging on a developer device.
•
It takes only marginally longer to load a program to a device over WLAN, LAN
or USB as it does to load it onto the emulator.
•
Any compiling work is usually avoided.
•
The device hardware is also included in the program test.
•
The finished program has been tested more effectively.
