ouldn't need to pay any
attention to the automationChild.
--
*From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Johannes Nel
*Sent:* Tuesday, May 15, 2007 5:37 AM
*To:* flexcoders@yahoogroups.com
*Subject:* Re: [flexcoders] Differe
om
Subject: Re: [flexcoders] Difference between getChild and
getAtomationChild
my guess its the interface for QTP
On 5/15/07, Tom Chiverton <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:
On Tuesday 15 May 2007, pmotzfeldt wrote:
> Hi, I am wondering what
Correct. getAutomationChild() is a method of the IAutomationObject
interface, and only returns children that also implement that interface.
IAutomationObject is part of the mx.automation package, which is designed
for automated testing. So basically, it's a filter for testing tools so they
only ha
my guess its the interface for QTP
On 5/15/07, Tom Chiverton <[EMAIL PROTECTED]> wrote:
On Tuesday 15 May 2007, pmotzfeldt wrote:
> Hi, I am wondering what the difference between a regular child and an
> automation child of for instance an UIComponent.
Some children are for purely GUI purpose
On Tuesday 15 May 2007, pmotzfeldt wrote:
> Hi, I am wondering what the difference between a regular child and an
> automation child of for instance an UIComponent.
Some children are for purely GUI purposes, such as a title bar or label.
--
Tom Chiverton
Helping to administratively repurpose br
Hi, I am wondering what the difference between a regular child and an
automation child of for instance an UIComponent.
What makes a child added become a automation child and regular child?
Thanks in advance!
6 matches
Mail list logo
