MSAA Roles map to Ranorex classes

Ask general questions here.
Posts: 357
Joined: Sun Dec 07, 2008 11:14 pm
Location: Dublin, Ireland

MSAA Roles map to Ranorex classes

Post by atom » Tue Dec 01, 2009 1:50 pm


The developers here are currently implementing MSAA to some of our custom MFC controls
So far they have got RanorexSpy seeing child elements on the control
However I have a question about Role and Capability....

From MSAA you can set a role for each element, how is this used by Ranorex to determine which class in the Ranorex API the control is now usable as?


User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: MSAA Roles map to Ranorex classes

Post by Support Team » Tue Dec 01, 2009 6:35 pm

Ranorex tries to match the MSAA roles to its own Roles, e.g. Button, Checkbox, etc. are mapped 1:1, some are mapped in a more general way, for example "Grouping" and "Pane" are mapped to Container.

MSAA elements always have the "Accessible" capability in Ranorex where you can access all attributes available via MSAA (e.g. exact msaa role, name, value, help, keyshortcut, defaultaction)

Have a look at my latest blog post: ... s-controls
While the article is for Winforms, the same principles apply to native MSAA implementations as well.

Ranorex Team