Hi,
We're developing an application that has some .NET and some MFC components.
Currently the application is started as an MFC application, but using a
managed message loop
(invoking Application::Run() in MFC's application class).
With this configuration we experience some problems with keyboard messages.
For example,
some WM_KEYDOWN messages (for example for arrow keys) does not make it
through to the
MFC window class. I've registered a message filter to the Application class
and I can see the message being received with the correct HWND handle. For
some reason, this message is later lost and is not
received by the WindowProc() method of the MFC window class. Interestingly,
all simple keys (letters) are received correctly.
Does anybody has any idea what is going on here?
(We've thought using the MFC message loop, but MS docs suggest using a
managed loop if .NET components are used).
Genady Beryozkin,
Algotec Systems.