Hi,

Using "automatically declare stage instances" rather than instance variables / programmatic naming.

Flash moaned about the latter - said I could not set the .name variable on something that had been added to the stage at authortime, which is why I assumed (maybe wrongly) that I could access the components from my parent using the on stage instance names - they all traced as null at ADDED_TO_STAGE for the parent. The only thing I can think here is that the load order may have something to do with it, which sounds wrong because I thought I had read ADDED_TO_STAGE is supposed to be called when everything is ready in a clip - including children. Thanks

   Glen

jonathan howe wrote:
Hi, Glen,

It would be interesting to know for triage: How are you referring to the
components in your main class, i.e.
- are your contributors using the "automatically declare stage instances"
or
- you are creating matching variables in the main class or
- not even giving them instance names and relying on the ADDED_TO_STAGE
handler to fire to 'make themselves known'?
-jonathan


On Mon, Nov 3, 2008 at 10:17 PM, sebastian <[EMAIL PROTECTED]> wrote:

forget to addChild()?

  The problem I have run into is that when I instanciate an AppScreen
symbol from my library - it's not on stage - and add it to the stage I
handle the ADDED_TO_STAGE event for wiring the components up.

 _______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders





--

Glen Pike
01326 218440
www.glenpike.co.uk <http://www.glenpike.co.uk>

_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Reply via email to