Ya. . I tried it on my project.



On Fri, Dec 5, 2008 at 7:57 PM, Roman Zilber <[EMAIL PROTECTED]> wrote:

> Venkata,
>
> Did you try to spy on tooltip?
>
> :)
>
>  On Fri, Dec 5, 2008 at 9:24 AM, venkata koduri <[EMAIL PROTECTED]>wrote:
>
>>  If your application uses a different class of object for the tooltip,
>> you may need to use the "Object Spy"(Tools-> Object Spy) to spy on the tool
>> tip to determine the class. After you
>> click the hand button on the Object Spy window, the mouse cursor will turn
>> into a hand icon.
>> Press and hold the CTRL Key to change the cursor to the normal state.
>> Mouseover the control
>> to bring up the tool tip. Once the tool tip is up, release the CTRL Key
>> and click on the tool tip
>> immediately, before it disappears.
>>
>>  On Fri, Dec 5, 2008 at 2:42 PM, mabobine <[EMAIL PROTECTED]>wrote:
>>
>>>
>>> This is the script that reads the text from tooltip
>>>
>>> Browser("Browser" ).Page("Page" ).Link("Link 1").MouseOver
>>> Window("nativeclass :=tooltips_ class32") .GetROProperty( "text")
>>>
>>> Can anyone guide me of how this script is generated. I know this is
>>> descriptive programming, but how can you say that the the tool tip
>>> native class is tooltips_class32. Obviously, one should know it before
>>> using descriptive programming.
>>>
>>> What if i want to see other window objects properties. From where
>>> should i see them. I used the object spy but it didn't detect tool tip
>>> at all.
>>>
>>> Guys! I hope you understand my concern.
>>>
>>> Regards
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Regards..
>> Venkat
>>
>>
>>
>>
>
> >
>


-- 
Regards..
Venkat

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
"QTP - HP Quick Test Professional - Automated Software Testing"
group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/MercuryQTP?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to