TrackPopupMenu on secondary UI thread

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   We use MFC Commandbars (v11.2) in our application and in addition to building an "ordinary" application (EXE-file) we also build an ActiveX control (OCX-file).

In order to meet several requirements on the OCX, the UI is run on a different thread from the main thread in the application hosting the OCX.

We have noticed that TrackPopupMenu behaves strangely in this scenario.
If you bring it up, but click outside the menu (and outside the OCX) but inside the host application, the menu will not close.

I noticed that a MouseManager is used and that the MouseManager installs a mouse hook. The mouse hook is installed on the thread that runs the OCX UI, which means that it will not detect mouse messages sent to the main application and the menu will not be closed.

Is there a controlled way to solve this problem?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
qliklars Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 July 2008 Status: Offline Points: 1	Post Options Post Reply Quote qliklars Report Post Thanks(0) Quote Reply Topic: TrackPopupMenu on secondary UI thread Posted: 23 July 2008 at 10:02am
	We use MFC Commandbars (v11.2) in our application and in addition to building an "ordinary" application (EXE-file) we also build an ActiveX control (OCX-file). In order to meet several requirements on the OCX, the UI is run on a different thread from the main thread in the application hosting the OCX. We have noticed that TrackPopupMenu behaves strangely in this scenario. If you bring it up, but click outside the menu (and outside the OCX) but inside the host application, the menu will not close. I noticed that a MouseManager is used and that the MouseManager installs a mouse hook. The mouse hook is installed on the thread that runs the OCX UI, which means that it will not detect mouse messages sent to the main application and the menu will not be closed. Is there a controlled way to solve this problem?