Groups | Blog | Home
all groups > dotnet interop > march 2006 >

dotnet interop : Key handling in local server object



Igor Tandetnik
3/27/2006 10:57:01 AM
[quoted text, click to view]

These accelerator keystrokes need to be delivered to WebBrowser control
via IOleInPlaceActiveObject::TranslateAccelerator. Apparently, one of
your hosts does that while the other does not.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925

Jeroen ter Hofstede
3/27/2006 4:52:45 PM
From our main application we're creating a COM component, written in C#
under .Net, which in turn contains a web edit control. This control acts as
an editor, and we can enter text in it. If we run it as an in-process
component, all works as expected, but when running out-of -process as a
local server (which we prefer due to architectural reasons) some keys are
not "seen" by the editor. This includes e.g. the Del key (backspace works
fine), Ctrl+C and Ctrl+V. Debugging reveals that the corresponding key
messages (WM_KEYDOWN and WM_KEYUP) are Dispatch()ed to the proper control.

Does anybody have a clue?

TIA,
Jeroen


Jeroen ter Hofstede
3/28/2006 12:00:00 AM
[quoted text, click to view]

Ok, thanks a lot!


Jeroen

AddThis Social Bookmark Button