Hi Muzak, I think what I've already decided (having slept on it) to go for something similar to your 3rd method - to restructure (class that behave like) A so that they can carry (and return) context info.
The reason I finally decided to go for that rather than Delegate is actually to deal with garbage collection; simply to make it easier for the coders using the API, as otherwise they'd have to track created Delegate objects so that they can be removed again, which is just an unnecessary headache. So; I'll try this through this iteration of the framework APIs and see how it goes. Thanks for your suggestions, Ian On 7/25/07, Muzak <[EMAIL PROTECTED]> wrote:
Third would be to have class A dispatch a custom event which holds the contextInfo, but this also means you'll have to pass the contextInfo to A in the first place (in B) and since you wanted to avoid that, I didn't mention this solution earlier.
_______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
