From: <[EMAIL PROTECTED]>
> Note also that the wParam contains a Unicode character expressed in
UTF-32.
> The documentation doesn't make this clear.
"doesn't make this clear" being a euphamism for "doesn't say it at all",
right? Or more accurately, blatantly contradicts? From MSDN:
"If wParam is not UNICODE_NOCHAR, return FALSE. The Unicode DefWindowProc
posts a WM_CHAR message with the same parameters and the ANSI DefWindowProc
posts either one or two WM_CHAR messages with the corresponding ANSI
character(s). "
This is therefore claiming that DefWindowProcW will use the same params for
WM_CHAR as was used for WM_UNICHAR. Since WM_CHAR does not use UTF-32, this
would mean that the docs do not correctly state the behavior? :-)
MichKa
Michael Kaplan
Trigeminal Software, Inc.
http://www.trigeminal.com/
