Any, I finally figured out a way of getting around this, which is to subclass the Unicode window, storing the keycode sent in WM_KEYDOWN and then constructing the corresponding Unicode character in WM_CHAR message (by calling ToUnicodeEx in certain circumstances, etc.), and it works fine in my own controls.

 

Unfortunately, the CodeJock Suite Controls don't do any such handling, and it would be a pain to have to subclass each one individually (particularly since they already use subclasses internally, and I'd rather not interfere with that). So I though a solution might be to install a thread-wide WH_GETMESSAGE hook and do the same kind of processing. The weird this is that, when I check the data sent with the WM_CHAR message intercepted by my hook, the Unicode characters are always set correctly. However, whether I return from the hook immediately or I call the next hook, the control (in this case a CodeJock FlatEdit control, which internally uses a standard Windows Edit control) eventually seems to receive a WM_CHAR with the wrong stuff (character code 63, as usual).

 

Does anyone have any experience with entering complex script text (particularly for the new Unicode-only locales that were added in Windows XP, such as Tamil or Gujarati?) into CodeJock Suite controls hosted in VB6?

 

What I ended up doing was a combination of hooking and subclassing (using the ComCtl32 subclassing functions, which are only supported on Windows XP or greater, but are very safe and don't seem to interfere with existing subclasses). First I install a WH_CALLWNDPROC hook (for the thread in which my VB6 UI is running) to intercept all WM_CREATE events, and I basically subclass any new window that gets created (making sure to remove the subclass when WM_DESTROY gets called). I also install a WH_GETMESSAGE hook (again, only for my UI thread), and whenever it gets a WM_CHAR message, it stores the hWnd and wParam values (which always seem to include the correct Unicode char). Then, in the subclass window proc, when I process a WM_CHAR message I compare the hWnd values and, if they match, I replace the incorrect wParam (which VB6 has probably messed up somehow) and replace it with the value I had stored.

 

If anybody is having trouble with complex script input with CodeJock controls in VB6, I'll be glad to send them code snippets.

i'm using 

-Codejock.Controls.Unicode.v15.0.1.ocx

-vb6sp6

if you have that please provide the community.

 

thank you,