Thanks. Doing it inline like that is nice.
On Fri, Sep 5, 2008 at 3:51 PM, Tracy Spratt <[EMAIL PROTECTED]> wrote:
> As Alex likes to advise, you can / should avoid binding when it is not
> necessary. You can do this assignment in-line, like this:
>
> <controller:MyController id="controller" hostContainer="{this}"
> creationComplete=" controller.services=this.module.services" />
>
>
>
> Tracy
>
>
> ------------------------------
>
> *From:* [email protected] [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Amy
> *Sent:* Friday, September 05, 2008 6:20 PM
> *To:* [email protected]
> *Subject:* [flexcoders] Re: Binding warnings - per instance suppression?
>
>
>
> --- In [email protected] <flexcoders%40yahoogroups.com>, "Richard
> Rodseth" <[EMAIL PROTECTED]>
> wrote:
> >
> > I like wiring things together in MXML, and I like having no
> warnings. Is
> > there any way to suppress binding warnings on a per-line basis?
> >
> > In the following case, "module" and "services" really aren't going
> to
> > change:
> >
> > <controller:MyController id="controller" hostContainer="{this}"
> > services="{this.module.services}" />
> >
> > The references are interfaces, and using custom events, I can add
> binding
> > support to those interfaces, but it's a bit unnecessary. I suppose
> I could
> > also set controller.services in a Script block, but I'm not crazy
> about that
> > either.
>
> I think Rick Winscott posted a link to his blog that showed how to
> filter your warnings. I don't think I bookmarked it, but it may be
> in the archives.
>
> HTH;
>
> Amy
>
>
>
