1

I have a holder movieclip, its base class is foo.

package {
    import flash.display.MovieClip;

    public class Foo extends MovieClip {
        public function Foo() {
            trace("foo");
        }
    }
}

Within foo are a number of other movieclips, with a base class of bar.

package {
    import flash.display.MovieClip;

    public class Bar extends MovieClip {
        public function Bar() {
            trace("bar");
        }
    }
}

I put a trace in the constructor of bar so I can tell if it's being loaded properly, and when I drag out foo onto the scene and run the clip, all the little bars within it fire off correctly. However, when I add it to the scene dynamically, such as like this in the Main class:

package {
    import flash.display.MovieClip;

    public class Main extends MovieClip {
        public function Main() {
            this.addChild(new Foo());
        }
    }
}

Suddenly, all the little bar movieclips within foo revert to regular old movieclips and don't fire. What's interesting is if you typecast one them as Bar at some point, and their normal class is set to Bar (within the movieclip itself, rather than base class), it works and the constructors all fire, like this:

    public function Main() {
        var foo:Foo = new Foo();
        stage.addChild(foo);
        foo.x = 0;
        foo.y = 0;

        trace(foo.getChildAt(1) as Bar);
    }//Main()

However, if you want multiple different types of Bar clips, and give each a base class of Bar, this won't work. They all spawn as generic movieclips. It DOES work if you go through and typecast them as either Bar1 or Bar2, but that means in practice you would have to try to typecast every child as every top-level object type every time you added the clip to the stage.

You also can't have a bunch of movieclips of the same type since Flash doesn't allow it, so each one needs to be a new class, and have that class typecasted when the parent is placed on stage. Kind of defeats the purpose of OOP.

This seems to be a bug in Flash itself, but is there any way to fix it?

double-beep
  • 5,031
  • 17
  • 33
  • 41
Lance
  • 13
  • 2
  • I'm not sure if this is what you mean, but have a look at this file. I think it might be what you are looking for. (and if it is I'll post it as an answer) http://www.megaupload.com/?d=A1OPFZDO – Zevan Dec 19 '10 at 23:10
  • It both is and isn't, there needs to be multiple types of bars with the base class of bar instead of just one. However, changing it to work that way does work, and it appears to be because you selected to export them on frame 1. Of course, this has the unfortunate side effect of needing to export all similar assets to frame 1 and making it more difficult for a preloader, but so far it's the best option I've got. – Lance Dec 19 '10 at 23:20
  • cool... fyi even though its oldschool the most reliable type of preloader is to create a stub movie - that is, a movie that loads your main movie - this solves the export on frame one problem. It might seem hackish but considering how much work it is to do a good preloader any other way, its a small price to pay. If you google for AS3 preloaders you'll see what I mean, lots of overlycomplex examples - not saying they don't work, just saying they're lots of work for a simple preloader. – Zevan Dec 19 '10 at 23:24

1 Answers1

1

The problem lies in your declaration of Foo's class members. If you want Flash to instantiate the elements as anything else than a MovieClip or Sprite, you must properly add a member declaration to the class, or declare the type when you use the new keyword.

This works:

package {
import flash.display.MovieClip;
import flash.utils.describeType;

public class Foo extends MovieClip {
    public var bar1:Bar1;
    public var bar2:Bar2;
    public var bar3:Bar1;
    public var bar4:Bar2;

    public function Foo() {
        trace("foo", this.numChildren);

    }
}
}

You can also just set the ActionScript preferences to "Automatically declare stage instances" and omit the class declaration, if your class doesn't really do anything special.

ActionScript is quite tolerant with types, but it seems the compiler ignores the types declared in the panel until it finds some kind of reference in the code, probably to prevent accidental bloating of the binary if someone forgot to erase a class name somewhere in the library.

weltraumpirat
  • 22,544
  • 5
  • 40
  • 54
  • This also works, was hoping to avoid it since it's a lot of tedium, but I can probably do the above until the final build, and then declare all the objects manually in the class. Thanks to both! – Lance Dec 20 '10 at 02:58