AX Viewer Seems to Intercept WM_SYSCOMMAND Messages

[jeffp]

I'm experiencing a weird situation in when I embed the ActiveX Viewer inside my application. This situation appears to be limited to Windows 7 OS, as it seems to work correctly in Windows XP.

It appears that any Windows 7 System Messages posted to the handle of my application goes to the ActiveX Viewer that I have embedded in my app.

For example, if I post the following message, where Handle is the handle to my application,

PostMessage(Handle, WM_SYSCOMMAND, SC_CLOSE, 0)

The message gets to my application if the panel containing the ActiveX Viewer object is not visible. However, if the ActiveX Viewer that I have embeded in my application is visible, the message never makes it to my application.

Does an embedded Active X Viewer receive these system messages? If so, is there a way to turn them off in the AX Viewer so that my application can process them.

[Vasyl - PDF-XChange]

Hi, jeffp.

This problem is reproduced (under Win7 only) and will be fixed in the next build. Please wait some time (~1 week) to the new build.

>> Does an embedded Active X Viewer receive these system messages?
No. But under Win7 we have some unspecific behavior with WM_SYSCOMMAND processing.
It looks like: Win7 cannot process the WM_SYSCOMMAND message in your application when the message-queue in your application contains other messages (which can be added by PostMessage for example). During processing we send (by PostMessage) special internal messages to the our ActiveX-container window. Therefore, when Win7 starts processing of the WM_SYSCOMMAND that message-queue sometimes can be nonempty (contain our internal messages also). In this situation Win7 stops processing of WM_SYSCOMMAND.

Thanks.

[jeffp]

I'm using the ViewerAX posted on 6/28/2010 and am still experiencing this problem when the ViewerAX is embedded in my application.

Has this issue been fixed on your end? If so, I'll need to dig deeper.

[Vasyl - PDF-XChange]

Hi, jeffp.

Please update to the latest version (2.0.54 build) - it may resolve your problem.

Best
Regards.

[jeffp]

Still happening with 2.0.54

[Vasyl - PDF-XChange]

Hi, jeffp.

We cannot reproduce this bug under win7.
Can you provide simple example for reproducing?

Thanks.