The following is my wish list for Flash Player 11. Â My agenda is making my job easier, and making the job of those who need to work with me, such as designers & middle-tier developers, easier. Â Additionally, I’d like to do things I couldn’t do in the past, or had to “fake” in the past.
Category: ActionScript
-
Fix for Ely’s SuperImage
SuperImage does not abort previous loads in it’s internal Loader. This means those Loader’s no longer have IOErrorEvent handlers. If you do have a case where the image fails to load after you’ve attempted to load a second image, this’ll cause an uncaught exception. This can happen when SuperImage is used within an itemRenderer where multiple image requests can occur during scrolling.
-
Make fl.containers.UILoader Use Image Caching
This is not code I’m proud of, nor have I thoroughly tested it. Â However, I know SOMEONE out there will need this, so here it is. Â Keep in mind, she leaks memory like a seive, but for a slideshow that shows to the user for 30 seconds, who cares. Â If you’re bored, you’re welcome to fix/mod/improve/re-write.
-
Error Handling in ActionScript 3: Don’t Make Grenades (or how to not crash Safari)
Preface
At the latest WWDC it was announced that the #1 reason Safari crashes for users is because of Flash, hence the new plug-in sequestering (i.e. if Flash blows up real good, it’ll do so in a way that won’t negatively affect the browser). I agree. If you’ve ever surfed the web using the debug Flash Player, Safari 3 and 4 explode all the time. I don’t know the true cause, but I do know when it’ll happen most often: when you get an error dialogue. These are shown only if you have the debug Flash Player installed, and an error that wasn’t “caught” happens. Sometimes hitting the “Continue” button vs. the “Dismiss All” button will work… but not always… BOOM! Â Thank God for History > Reopen All Windows from Last Session. Â Here’s how you can help prevent Flash’s bad name from getting worse (that and until Adobe makes it more stable).