L PROTECTED] On
> Behalf Of ben.clinkinbeard
> Sent: Saturday, August 25, 2007 12:08 PM
> To: flexcoders@yahoogroups.com
> Subject: [flexcoders] Re: Using [Event...] in Custom Classes
>
>
>
> Yea, I guess I am just going to have to fall in line with my
> constant-naming practi
ter? If not, I suggest filing it at
http://bugs.adobe.com/flex.
- Gordon
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of ben.clinkinbeard
Sent: Saturday, August 25, 2007 12:08 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: U
Yea, I guess I am just going to have to fall in line with my
constant-naming practices for now, but I think its something that
should be fixed. The whole point (besides code hinting) of [Event]
tags (and the type attribute specifically) is to give the compiler
info on where to go look for those val
Ben,
I appologize. I was way off on this one. I made a bad assumption based
on my ignorance.
Do you ever wish you could take back a post? :)
Tony
ben.clinkinbeard wrote:
>
> Event metadata is definitely not ignored in AS. Take a look at just
> about any class in the framework and you'll see p
Yeah, here's the way I think it works in the current FB 3 release anyway
(which is the way ben described too):
You put metadata in your class, something like:
[Event(name="myEvent", type="com.me.MyEvent")]
So then you type: myClass.addEventListener( and then the auto events come up
in the list t
ok, I see your point. I did not look at it that way. So, it is a bug then.
ben.clinkinbeard wrote:
>
> Event metadata is definitely not ignored in AS. Take a look at just
> about any class in the framework and you'll see plenty [Event] tags.
> It is there specifically to provide code hinting and
] Re: Using [Event...] in Custom Classes
Event metadata is definitely not ignored in AS. Take a look at just
about any class in the framework and you'll see plenty [Event] tags.
It is there specifically to provide code hinting and support for
binding in MXML.
The problem here is that the
Event metadata is definitely not ignored in AS. Take a look at just
about any class in the framework and you'll see plenty [Event] tags.
It is there specifically to provide code hinting and support for
binding in MXML.
The problem here is that the code completion engine is offering class
constants
8 matches
Mail list logo
