But it's antipattern and I believe event model should be used in this cases. Calling method from the parent scope is bad design. I consider either event model or utility class could be used. It depends on particular case.
On 8/15/06, Gordon Smith [EMAIL PROTECTED] wrote:
You can also
Subject: [flexcoders] Re: Best way
to reference items in a parent MXML component?
How would a child call a function in the parent
though? Events don't
seem (semantically) like the right thing because I basically just want
to use a utility function defined in the parent. Like I have a
function
PROTECTED]ups.com
Subject: [flexcoders] Re: Best way
to reference items in a parent MXML component?
How would
a child call a function in the parent though? Events don't
seem (semantically) like the right thing because I basically just want
to use a utility function defined in the parent. Like
If you want to use utility function, make the utility class with
static methods only and place the function there instead of parent
class. Then call it from children via MyUtilityClass.myMethod();
On 8/13/06, ben.clinkinbeard [EMAIL PROTECTED] wrote:
How would a child call a function in the
way
to reference items in a parent MXML component?
How would a child call a function in the parent
though? Events don't
seem (semantically) like the right thing because I basically just want
to use a utility function defined in the parent. Like I have a
function that I am using to format
5 matches
Mail list logo
