When you compile an app using Unicows, the ability to properly close the menu is lost on Windows 95/98 and ME.  The only way to close an expanded menu is to left mouse click on the title bar.  I added the following code to the application, which resolves the problem.  However, adding the OnWndMsg override prevents any ON_XTP_EXECUTE to work.  Is there a solution to this?

Added code:

BOOL CMainFrame::OnWndMsg(UINT message,WPARAM wParam,LPARAM lParam,LRESULT* pResult)
 {
 // Handles Menu problem on Windows 9x when using UNICODE/UNICOWS
 if(XTPMouseManager()->IsTrackedLock())
      {
      switch(message)
           {
           case WM_ACTIVATEAPP:
                          if(!wParam)
                               XTPMouseManager()->SendTrackLost();
                          return(FALSE);
           case WM_SYSCOMMAND:
                          if(wParam == 0 || LOWORD(wParam) != 0)
                               XTPMouseManager()->SendTrackLost();
                          return(FALSE);
           case WM_COMMAND:
                          if(wParam == 0 || (LOWORD(wParam) != 0 && HIWORD(wParam) == 0))
                               XTPMouseManager()->SendTrackLost();
                          return(FALSE);
           }
      }
 return CWnd::OnWndMsg(message,wParam,lParam,pResult);
 }

I found a better and more reliable method to take care of this problem.  Boy, Unicows/Unicode and this Tookkit Pro sure does clash a lot!  Never had these problems with Xtreme toolkit.

copy code from XTPFrameWnd.h.

What is base class for CMainFrame? Why you call CWnd::OnWndMsg(message,wParam,lParam,pResult); instead of CFrameWnd I think it is cause of your problem.

Oleg

I had CFrameWnd before, and changed to CWnd just to see if it made any difference.  But I had the same problem.  The logic works as far as resolving the Windows 95/98/Me menu problem, but prevents ON_XTP_EXECUTE from working on all systems, including XP.  However keep in mind that I believe this only affects programs compiled with Unicode with Unicows support.

call CXTPFrameWnd::OnWndMsg instead of CWnd::OnWndMsg. I think it must solve your problem.

Oleg

Yes, that does work.