Page 1 of 1

How to identify custom user controls with the AutomationPeer

Posted: Wed Dec 19, 2012 4:19 am
by JessieT
Hi,

By using Ranorex spy, it cannot identify the custom user controls for Win8 Apps.

By reference the link,
http://msdn.microsoft.com/en-us/library ... l/jj219211
we added the automationPeer for all custom user controls. But not work for Ranorex spy. Any idea how to do that?

Thanks

Ranorex version: 4.0
OS version: WIn 8

Re: How to identify custom user controls with the AutomationPeer

Posted: Thu Dec 20, 2012 11:51 am
by Support Team
Hello,

Please make sure that you start 'Ranorex Spy' with administrative rights.
Furthermore, please take a look at section 'General Troubleshooting' in our User Guide.

Could you please try to identify your custom controls with 'Microsoft Inspect'?
Please take a look at 'Inspect' on MSDN.

Regards,
Markus (T)

Re: How to identify custom user controls with the AutomationPeer

Posted: Mon Dec 24, 2012 10:23 am
by JessieT
Hi,

Thanks for your reply.

Yes, we launch the spy with administrator rights but it cannot identify the custom controls. With the 'Inspect' , those custom controls can be identified.

Regards,
Jessie

Re: How to identify custom user controls with the AutomationPeer

Posted: Mon Dec 24, 2012 12:25 pm
by Support Team
Hello,

Thank you for reporting that issue. In order to reproduce it, we would need more information.
Is it possible to get the application to analyze the issue in more detail?
Additionally you can try to install the bug fix version 4.0.1. of Ranorex and try it again.
Thank you!

Regards,
Bernhard

Re: How to identify custom user controls with the AutomationPeer

Posted: Tue Dec 25, 2012 2:21 am
by JessieT
Hi,

I installed the 4.0.1, this issue still existed.

Regards,
Jessie

Re: How to identify custom user controls with the AutomationPeer

Posted: Thu Dec 27, 2012 11:21 am
by Support Team
Hi,

Is it possible to get the application to analyze the issue in more detail?
You could send it to our support mail address: [email protected].

Thanks,
Markus