Comments on: Watch “Export in First Frame” when creating components

By: BIll

BIll — Sat, 03 Apr 2004 07:47:02 +0000

What about dataBindingClasses made from xml sockets and dataSet components? When I uncheck this component flash spits out a bunch of errors.

By: Rob Edgar

Rob Edgar — Thu, 22 Jan 2004 10:35:44 +0000

I have also had the same problem, even when things are not set to export on Frame1.

This is so common in the end I have resorted to only having one component per fla.

Even then I stil get problems from time to time with the generated swc’s NOT picking up changes I made in the fla (testing works fine in the fla but just the exported version wont update), to fix this when it happens I have to create a new fla and copy all the library items to the new fla and the generate the swc.

Another quirk I have come across with 2004 components is in the “extends” clause.
For example try the following

import com.me.y;
class com.me.comp.x extends y

import com.me.y;
class com.me.comp.x extends com.me.y

In the former everything is Ok but in the later you will find that no inherited properties show up in the component inspector, however your component works fine and actually has the correct inheritance.

By: eokyere

eokyere — Thu, 22 Jan 2004 08:50:41 +0000

i experience this from time to time too… what i have realized though is that this happens to me when I have 1-frame swfs that have slightly heavy processing.

when i allow a couple of “buffer” frames with the same flas, i seem to overcome the problem. still, it is quirky. i’ll experiment with your suggestions here

By: Keith Peters

Keith Peters — Thu, 22 Jan 2004 07:38:46 +0000

Wow. I ran into the exact same thing today. I made one component, and it worked fine. Made a second one in the same fla and both stopped working. I was going insane after rebuilding both almost from scratch. Finally I noticed that I had the bounding box mc set to export. Unchecked that and all was fine. Any insight onto WHY this happens? I don’t get that at all.