I believe this is because the ASDoc compiler takes less passes at the
code base than the regular compiler does.
One of the missing passes is the one that processes [Bindable] tags and
adds the Event dispatching code.
I'd be wary of doing it the way you described since out in house binding
guru reported a bug that occurs under those circumstances.
Make it explicit and you have no problems.
Gk.
Gregor Kiddie
Senior Developer
INPS
Tel: 01382 564343
Registered address: The Bread Factory, 1a Broughton Street, London SW8
3QJ
Registered Number: 1788577
Registered in the UK
Visit our Internet Web site at www.inps.co.uk
blocked::http://www.inps.co.uk/
The information in this internet email is confidential and is intended
solely for the addressee. Access, copying or re-use of information in it
by anyone else is not authorised. Any views or opinions presented are
solely those of the author and do not necessarily represent those of
INPS or any of its affiliates. If you are not the intended recipient
please contact is.helpd...@inps.co.uk
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of foobone9
Sent: 13 February 2009 02:02
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Does ASDoc process metadata tags?
I have classes that are marked with [Managed] and [Bindable] tags.
Even though these objects do not extend eventDispatcher I can call
dispatchedEvent, addEventListener, and removeEventListener on them. I
assume this is because the compiler is wrapping the dispatch code
around the object when it sees the metadata tag.
This works fine in Flex Builder but when running ASDoc it serves up
these calls as errors. Is there a flag I need to set for ASDoc to
process the tags when compiling the objects?
