I can't say that I fully understand the distinction between the two, but I have
found that sometimes this.parentDocument works better than this.parent
Hope that helps,
Sid
- Original Message
From: andrewedwards39 [EMAIL PROTECTED]
To: flexcoders@yahoogroups.com
Sent: Monday, July
@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Sid Maskit
Sent: Tuesday, July 15, 2008 3:40 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Accessing public function from a different
mxml
I can't say that I fully understand the distinction between the two, but
I have found
Try using parentDocument instead of parent to go up the MXML hierarchy.
Or try dotting down from the Application instance:
Application.application.foo.bar.a.pubfunction().
Gordon Smith
Adobe Flex SDK Team
From: flexcoders@yahoogroups.com
.
Tracy
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Sid
Maskit
Sent: Tuesday, July 15, 2008 3:40 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Accessing public function from a different mxml
I can't say that I fully
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Scott
Sent: Tuesday, July 15, 2008 2:13 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Accessing public function from a different
mxml
I'm working on the same issue right now
, July 15, 2008 2:08 PM
To: flexcoders@yahoogroups.com
Subject: {Disarmed} RE: [flexcoders] Accessing public function from a
different mxml
This may be the time to learn about the singleton pattern/class if you
are not familiar with it. I discovered its benefits only recently,
and it is quite
6 matches
Mail list logo