[RESOLVED] addChild to specific frame?

[5TonsOfFlax]

I'm using script to replace some TextFields with instances of another class at runtime. Basically calling:

var par:DisplayObjectContainer = textfield.parent;
var idx:int = par.getChildIndex(textfield);
//remove tf from parent
par.removeChildAt(idx);
//add self in place!
par.addChildAt(this, idx);

In my code I'm also adding the textfield as a child of the new instance, but I'm pretty sure that doesn't matter to this issue. Also possibly important, the parent seems to be MainTimeline. The problem is that the new instances appear on all (subsequent?) frames, whereas the TextFields they replaced were only on a particular frame. Is there a way to preserve the frame association?

[joshstrike]

my guess would be ... and I'm new at this too ... try instantiating a new version of the same top-level class with each frame, named for the frame number, and then call it locally? I never work with frames so this is one I'm probably never going to get too good at...

[Cimmerian]

//add self in place!
par.addChildAt(this, idx);
???

[5TonsOfFlax]

//add self in place!
par.addChildAt(this, idx);
???

I'm not sure what you're trying to say. This code is an excerpt from a class which extends MovieClip (called SelectableText in my code), and wraps a TextField to add behaviors to it. "this" in the code above refers to the new instance of that class, which is processing the TextField which it should wrap.

Since writing my initial post, I have also discovered that not only do the new SelectableTexts appear in all frames, when returning from a different frame to the original frame, the original TextFields are back, each showing both in the SelectableText AND as it originally was. I think I'll have to do the conversion at authoring time using jsfl instead of at runtime, which seems to have too many side effects.

[senocular]

As far as I know, this technique only worked for ActionScript 2. The process by which the timeline handles timeline-based instances has completely changed and, I'm pretty sure, is hidden from the user meaning there's no way to dynamically create an instance at runtime and associate it with another instance's timeline definition.