MSAA and application menu

We had a similar issue, coming from Stingray Toolkit (which had its own menu peculiarities), however, we use MicroFocus SilkTest, so I cannot be more specific for MSAA. I will describe what I found and did, instead of trying to match that with what you have.

In a nutshell, as far as I can figure out, CodeJock only uses the initial menu load to create a menu bar (CXTPMenuBar) that contain lists of controls. After loading, no menu resource (a la Microsoft menu HMENU) are used, and the menu bar/controls are used for drawing the menus.

To workaround this, we have a dynamically loaded SilkTest extension DLL that is loaded by the application (if not there, no QA so no error). This DLL exposes a function called by SilkTest to initiate a menu. The menu to select is specified by a text string, like:

/File/Do Foo

or

/File/[cmdid]

or

/File/{idx}

where [cmdid] is the command id, and {idx} is the index within the menu.

We then get the CodeJock menu bar controls:

GetCommandBars()->GetMenuBar()->GetControls()

and traverse the controls. At this point, we dump out a key sequence which is used to select the menu (why this is so I explain below). In your case, since it is multi-lingual, you cannot use "/File/Do Foo", but more likely just "[cmdid]". This will need to locate the control in the menu bar controls via FindControl(). I suggest you then go back through the parent control(s) to be able to determine the full key sequence which is used to select the menu.

The reason for using the key sequence is so that the menu will actually display (vs just firing off a PostMessage() with the command id), so that command UI updates and control drawing is performed. It also gives the QA person doing the scripting a chance to see what their script and their menu selection is doing (SilkTest allows you to set the keystroke delay).

What you wind up with is this key sequence (for above example):

<Alt><Down><Down><Down><Enter>

Another like "/Edit/Do Bar" might be:

<Alt><Right><Down><Down><Down><Enter>

which will select the menu. Now for the secret sauce with this - the way the CodeJock menu bar activates is rather weird, and although this key sequence would work if you type it, being sent via send keys does not work. What I found was it was necessary to position the mouse over the first menu bar entry, otherwise the sequence would not work correctly (positioning done by SilkTest TypeKeys function). Code snippet:

CWnd*            pMainWnd;     CXTPMenuBar*    pMenuBar;     CXTPControl*    pControlMenu;     BString            strKeys;     RECT            rect;     POINT            point;     // retrieve the main window     pMainWnd = CWnd::FromHandle(hWnd);     // retrieve the menu bar for the window     pMenuBar = ((CXTPMDIFrameWnd*)pMainWnd)->GetCommandBars()->GetMenuBar();     // get the first control     pControlMenu = pMenuBar->GetControls()->GetAt(0);     // get the control's bounding rectangle     rect = pControlMenu->GetRect();     // set the click point to middle     point.x = (rect.left + rect.right) / 2;     point.y = (rect.top + rect.bottom) / 2;     // convert to window ccordinates     ::ClientToScreen(pMenuBar->m_hWnd, &point);     ::ScreenToClient(hWnd, &point);     // prepend the menu accessor and append the menu select     strKeys  = KEY_ACCESSMENU;// = <Alt>     strKeys += pszKeys;     strKeys += KEY_SELECTMENU;// = <Enter>     // and pick it     QAP_TypeKeys(hWnd, (LPTSTR)strKeys.c_str(), &point, EVT_SETFOCUS);

I hope that helps.

If you want the menu to act as a 'native' menu (HMENU based, and possibly wrapped by CMenu), you will not be able to use the CodeJock command bar/menu bar since they do not use HMENU except when they initially load the menu resource.

Other CodeJock folks chime in to correct me, though I went through this pretty closely