nyway.
-Original Message-
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf
Of dnk
Sent: Sunday, January 18, 2009 10:36 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] flex not seeing method - update
Are there any examples anywhere?
On 18-Jan-09, at
flexcoders@yahoogroups.com
> Sent: Monday, January 19, 2009 12:16 AM
> Subject: Re: [flexcoders] flex not seeing method - update
>
> Tried that, and same issue.
>
> d
>
>
>
> On 18-Jan-09, at 10:54 AM, Paul Andrews wrote:
>
>> Try making the handler pu
> prefix the element name with the outerDocument keyword.
>
> Paul
>
> - Original Message -
> *From:* dnk
> *To:* flexcoders@yahoogroups.com
> *Sent:* Monday, January 19, 2009 12:16 AM
> *Subject:* Re: [flexcoders] flex not seeing method - update
>
> Trie
renderer or item editor, you
prefix the element name with the outerDocument keyword.
Paul
- Original Message -
From: dnk
To: flexcoders@yahoogroups.com
Sent: Monday, January 19, 2009 12:16 AM
Subject: Re: [flexcoders] flex not seeing method - update
Tried that, and same issue
Tried that, and same issue.
d
On 18-Jan-09, at 10:54 AM, Paul Andrews wrote:
Try making the handler public..
The tag is, let's call it... Voodoo :)
What it's actually doing is defining a new custom component class, whereas
every other MXML tag you use will define elements of the class defined in
the root element of your MXML document. You can tell MXMLC what name you'd
like the class to have in order to
- Original Message -
From: "dnk"
To: "Flexcoder List"
Sent: Sunday, January 18, 2009 5:47 PM
Subject: [flexcoders] flex not seeing method - update
>
> Ok, I found one additional piece of info that when I sent this I
> thought was not relevant. In my main.mxml, my component.mxml is
> ac
7 matches
Mail list logo
