I think the root movie clip does extend UIObject, as createClassObject
works for me. And the objects I'm creating aren't custom ones, but
things like mx.controls.ComboBox, so I don't have to worry about
symbol* variables.
I may have to look into UIObject a bit more. I've been making some of
my
createClassObject and createObject (and a few more) methods are defined in
the mx.core.ext.UIObjectExtensions class, and are added to MovieClip's
prototype when UIObjectExtensions gets 'initialized'. This happens, if you
have a UIComponent in your library. So createClassObject method will work,
createClassObject is defined in UIObject core object. I don't think it can
be called as a method of any movieclip. It also requires that you define
static var symbolName : String = linkageID;
static var symbolOwner : Object = com.myclass;
and at the end of the day It calls createObject
Just to amend my previous comment, in the case where I said
`createClassObject()` failed but `attachMovie()` didn't, that ended up
to be not quite true. `createClassObject()` didn't do anything, but
`attachMovie()` created the visual portions of the clip, but it looks
like none of the
4 matches
Mail list logo
