I’ve decided to put up a post for every bug I find in the current Flash Extension API - there’s a lot of them and it’s worth jotting stuff down for other Flash JSFL developers. (All 3 of us *wink*). This bug is in the timeline.setSelectedFrames() method.

Certainty: 98% certain it’s a JSFL bug. I usually mess with this stuff more to be sure, but I have found it getting tweaky on me in about 6 different Flash extensions I’ve been working on, and I’ve stopped the code in mid-stream at the point that the API should have made it’s frame selection using the “setSelectedFrames()” command… but no luck.

Problem: Run some JSFL code, somewhere in it I use the timeline.setSelectedFrames([layernum,startFrameNum,endFrameNum]) format of the command. I haven’t pinpointed the specific bug-trigger, but I suspect it has something to do with how the API has problems updating it’s view of the currently active timeline. I will explain this more in another post about a JSFL bug having to do with adding multiple keyframes to a timeline. For now, be aware that this method works 95% of the time… but in some odd circumstances it just refuses to work properly. If you encounter it, you can test it by stopping the code just after the line where you make your selection call. (Test the values for layernum, startFrameNum, endFrameNum just to be sure, but you will find they are legal and it’s a language bug, not a problem with your code logic.)

As a side note, other forms of the command don’t seem to cause the same errors. That is a damn good thing, too, cuz it makes the work-around a snap.

Bug Workaround: Fortunately, the solution is very simple. Use the same values as before and make use of following commands instead…

timeline.currentLayer = layernum;
timeline.setSelectedFrames(startFrameA,startFrameB);

So there you have it. This is one of those cases where knowing of a bug is more important that finding a solution to it, cuz the solution is so obvious. But man, I can’t tell you what a pain-in-the-arse it is to not know of it. Avoid using the extended form of the timeline.setSelectedFrames() method, and you will breathe easier.

So it’s been a few weeks since my last post, and I’ve got the new version of the Symbol-To-Frames command ready for release. The code is tighter. Less prone to bugs. Fewer calories. Tastes great. If you’ve already got it, I suggest getting it again as this version is better…

But before I send you to the updated Flash extensions link, I need your opinion. It’ll only take you 30 seconds, and if you don’t do it you will start kicking people in the head later on for not doing it. Including yourself. Friends don’t let friends kick themselves in the head. So read on or skip down to the survey link and take the 30-second survey. If you’re in a hurry, only the first 2 questions are required:

Flash Extension Version and OS Survey

Otherwise, read on. Here’s the current challenge:

I used to develop these extensions for Flash 8, before Flash CS3 arrived. And ever since CS3 was released, I switched over… figuring that as long as I stuck to the Flash 8 API command-set (don’t worry if this sounds mumbo jumbo, it will all get clear in a second), whatever extensions I built in CS3 would work in Flash 8. Not true. The Flash API is what makes building these extensions possible. And, er, impossible…

Fact: The Flash Extensions API is a tweaker. It’s more jittery than Grandma on meth. There are lots of bugs in the JSFL programming langauge itself, and while I can find ways to get around a lot of these… it takes a lot of time to do so. The real problem is that depending on which version of Flash you use, the bugs are different. And if that wasn’t tedious enough, the operating system you use can throw different bugs as well.

Here’s one potential solution: Develop for fewer platforms…

Stop developing for Flash 8, Macs, and/or older Mac & PC operating systems. That could be YOU. Either way, I decided to set up one of those survey monkey questionaires to collect the answers and make my decision. I’m doing the cheapo free version of Survey Monkey, so after the first 100 answers, it ends. (And I already emailed the awesome folks on my list, so time is running out!) So please, if you are reading this, take 30 seconds and answer a few very quick questions. In return, you’ll get cool free Flash extentions that work on your version of Flash. Here’s the link:

Flash Extension Version and OS Survey

Thanks for taking the time… and if you have any thoughts about extensions you’d like to see developed, there’s room for ideas on the survey.

Now then, the latest version of the FlashWhip SymbolToFrames extension only works with Flash CS3 (and it’s now available on the downloads page). If you want me to keep building for 8 or MX 2004, be sure to fill out the survey.

Some important news for you folks regarding more FlashWhip Flash extensions and updates:

First: My blog comment system has been on the fritz. After a little tweaking, it is working again. I’m really bummed it has been down the last few weeks cuz I really want to get as much feedback as I can so that I can keep building cool tools. If you have any important Flash extensions that you want, PLEASE leave me your thoughts and comments…

Second: There is an upgrade to the FramesToSymbol flash extension available in the downloads page.

Third: There is a small glitch in the SymbolToFrames command that I built. Not a big deal. If the symbol you are extracting from does not have layers of equal length, those layers are pasted in with equal length when they are extracted via the SymbolToFrames tool. That means it adds extra frames to the end in some cases. I will fix this when I have a chance next week.

Fourth: this is important–some folks have reported trouble installing the Flash extensions which could be due to a lack of the proper Adobe Extension Manager. OR it could be something to do with the version of Flash that you are using. OR I could have mussed the pooch and built the MXP file wrong. I hoped I would have a chance to work on this today before my web contact is gone, but I had to get my comment system going again.

Fifth: I’m going to be out of radio contact for a few days. No easy access to web or cell or nothin’. (Yes, there are still places like that on this Earth– unbelievable, ain’t it?) So if I’m slow to respond to folks, please understand that I’ll respond to all your questions as soon as I return. If you want an update, I will be sending out to my list as soon as I am back and I have a chance to fix all those errors.