I have never seen any properties captured in ActiveX tab when using GUI spy. I have tried to select ActiveX add-in when starts WR, but it doesn't seem to make any difference. Does any one know why? I have WR 7.5.
Follow the steps you can see the Active X properties.
1) open the winrunner with Active-X AddIn
2) open the Flight A application supplied by WinRunner. Login into the appliation.
3) open the gui spy from tools
4) select the Active-X tab on spy
5) select the spy button and point on the "Date of Flight" first field on "Flight Reservation" application.
You can view the Active-X properties of the field.
I was clear enough in my answer. [img]images/icons/smile.gif[/img]
If you want a high quality software system, you must ensure each of its parts is of high quality. by Watts S. Humphrey
I did see ActiveX properties from the sample application.
But I am not able to see
ActiveX properties from our own application. I followed WinRunner user guide on how to work with ActiveX controls ( install ActiveX, then load ActiveX add-in, start WinRunner first, application 2nd) and it doesn't work.
I installed a patch from Mercury support and was told only to load VB add-in when starting WinRunner. After installing this patch, we are still not able to see ActiveX properties on ActiveX controls when using GUI spy, but we are able to use ActiveX_get_info to retrieve properties. I also found the patch has changed the way WR records GUI map. It only records vb_name for a GUI object and ignores settings in GUI map configuration.
I am not sure if I should carry on using ActiveX or to find workround.