Re: WM_GETTEXTLENGTH change in winproc.c
19 Aug
2001
19 Aug
'01
12:12 a.m.
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 ? Gerard
8880
Age (days ago)
8880
Last active (days ago)
0 comments
1 participants
participants (1)
-
Gerard Patel