WM_GETTEXTLENGTH change in winproc.c
gerard.patel at nerim.net
Sat Aug 18 19:12:30 CDT 2001
At 02:35 PM 18/08/2001 -0700, you wrote:
>For standard controls like buttons it should never be a problem since
>there is both an ASCII and Unicode win proc, so in a pure ASCII app we
>should never do the conversion. I think the problem is that the
>dialog code does a CreateWindowW, so the button is Unicode even though
>the app does everything in ASCII. I guess we'll have to maintain both
>A and W win procs inside each window, not only inside the class.
How about creating Ascii windows when the app calls DialogBox..A variants ?
More information about the wine-devel