Re: Edit windows created with CreatwWindowExA become Unicode windows when manifest active
- From: "Jeff Partch [MVP]" <jeffp@xxxxxxxx>
- Date: Fri, 24 Mar 2006 07:27:16 -0600
"David Liebtag" <DavidLiebtag@xxxxxxxxxxxxx> wrote in message
news:eXSBY9vTGHA.5900@xxxxxxxxxxxxxxxxxxxxxxx
I have discovered that if I try to create a multibyte edit window with
CreateWindowExA on XP with a manifest active, then IsWindowUnicode reports
that the window is a Unicode window. When pasting, the window correctly
receives multibyte data. However keyboard input sends Unicode data to the
window.
Is there a way to stop this from happening? For various complicated
reasons, my application requires multibyte operation in its edit windows.
I bugged MS about this repeatedly back in late 2002 and here is what they
said...
"The V6 edit control is unicode only, when building an non-unicode
variant of our application, you'll still get the unicode edit control
because of the inclusion of the manifest. ... While the documentation
doesn't seem to just come out and say it, if you want to use the new V6
common controls, your project should be built for unicode. We've got a
doc bug reported against this too".
Back then, my tests with IsWindowUnicode were returning FALSE, but it
wouldn't surprise me if they silently implemented a fix to 'correct' that.
--
Jeff Partch [VC++ MVP]
.
- Follow-Ups:
- References:
- Prev by Date: Re: WM_EXITSIZEMOVE and WM_SYSCOMMAND
- Next by Date: Re: Edit windows created with CreatwWindowExA become Unicode windows when manifest active
- Previous by thread: Edit windows created with CreatwWindowExA become Unicode windows when manifest active
- Next by thread: Re: Edit windows created with CreatwWindowExA become Unicode windows when manifest active
- Index(es):
Relevant Pages
|
