Update: I posted some additional information about the Inspectable issue.
So I’m working on some components, and they have Inspectable tags on all the properties that are customizable. Nothing new or exciting here… except that one particular component has a large class heirarchy with well over a hundred properties. Just about every time I mess with one of these properties, Flash starts acting up, and sometimes it even crashes without warning. After trying everything imaginable to track down the problem, I believe that Flash 8 is just having trouble handling so many properties at once.
Originally, I figured Flash was choking on some of the legacy assets in the library. There’s a lot of AS1 code floating around, and since I didn’t work on any of the art assets, there could be all sorts of evil lurking in the dark corners. So, to be extra sure, I created a brand new FLA, and made a new symbol for my component from scratch. I didn’t add any art, it’s just the component on a blank symbol.
After I set the class in the Component Definition dialog, everything is looking good. Then I try to save the FLA. It appears to work, except for one detail: The asterisk that says my file has been modified didn’t disappear. It’s definately not anything in the art. I’ve been hitting this fork in the road for the last two weeks, art or no art. I can continue working and hope that it works the next time I try to save the file (or the FLA gets corrupted and I have to start from scratch or get it back from CVS), or I have to close my FLA and open the last saved version to try doing the same thing over again.
Unfortunately, that’s the better behavior from Flash. Every once in a while, Flash will completely crash on me. Most of the time, Windows throws up that nice little “Ha, ha! Your program sucks! Do you want to tell us about it?” dialog. Usually this happens if a click on the stage somewhere after messing with some properties. Sometimes Flash just closes without any warning whatsoever while I’m compiling my SWF. I’ll just look at the taskbar and notice that it’s gone.
As far as I can tell, no one else is having this problem. I’ve done quite a few Google searches. The only thing I found that sounds anything like this behavior is in the Release Notes for the Flash 7.2 update. In the “Crash Issues Addressed” section, it says 96110 : Component property definition with Inspectable value incorrect will cause crash.
As far as I know, all my Inspectable tags are correct. The only thing I’m not sure about is where exactly to use quotes, or if it even matters. Every tutorial for Inspectable is different.
Has anybody else faced problems working with Inspectable, or does anyone from Macromedia know of continued issues with Inspectable causing crashes?
I personnaly noticed that the Flash IDE react strange and slow when you have a Symbol in your library selected (displayed also in the mini-preview) that contains symbols that have live-preview enabled on them.
just my 2 cents
The original project had a live-preview for the component’s symbol, but in my simplified version, my symbol had no live-preview and no content on the stage. You’ll see in my followup post that I found the cause, and I was defininately on the right track when I guessed that it was the Inspectable meta-tag.
I noticed the same thing with the [Inspectable] tag with variables encapsulated with anything but the double quote character (“). i.e. make sure it’s something of the sort:
[Inspectable(name=”parameter name”]
I actually noticed something very similar in flash 8. On one specific machine if I drag a component onto the stage from the component library flash will crash miserably, sometimes not right away, sometimes you have to click on it or move it before it crashes. Other machines it works perfectly fine when you add it to the stage. Did anyone ever find a solution?
Actually found the answer elsewhere :
If the component creates a trace message on creation, and the output panel isn’t open, it will crash Flash. I have posted this bug to Macromedia, but nobody seemed to care. Its a big problem when you open a FLA with it already in it and the output is closed, as you’ll have to open Flash first, then open the output panel, then open the Fla.
Thanks, Richard. Good to know.
This article is almost 2 years old now, but I’ll post anyway…
I’ve noticed this same thing in MX2004, 8, and now CS3. Flash mostly crashes for me when I check or uncheck the lock in the properties pane to (un)constrain the dimensions when resizing a movieclip. Doesn’t do it from the Transform pane. After reading this, I did notice that it only happend when the Output panel is closed as well.