abmUseUnicodeStrings function
|
Remarks
|
Specifies to the SDK if it must interpret the strings passed to its functions as UNICODE (two bytes per character) or ANSI (one byte per character): by default strings are interpreted as ANSI. Note that strings returned by the SDK will be always in UNICODE (BSTR).
|
|
Return value
|
None
|
|
Syntax
|
void abmUseUnicodeStrings (
BOOL bUseUnicode
);
|
Parameters
|
Description
|
|
bUseUnicode
|
Boolean value that specifies the kind of strings passed. Supported values are the following:
|
Value
|
Meaning
|
|
FALSE (0) (default)
|
Strings are interpreted as ANSI.
|
|
TRUE (1)
|
Strings are interpreted as UNICODE.
|
|
|
Here follows a little Visual Basic 6 sample that demonstrates the use of this function; as you can see the following lines set two captions to two different Push buttons using the default ANSI interpretation of strings
abmSetCaption Command1.hwnd, "Key 1"
abmSetCaption Command2.hwnd, "Key 2"
The following lines of code will tell to the SDK to interpret the strings passed as UNICODE
abmUseUnicodeStrings True
abmSetCaption Command1.hwnd, StrConv("Key 1", vbUnicode)
abmSetCaption Command2.hwnd, StrConv("Key 2", vbUnicode)
