I’ve been too busy to Blog this earlier, but an article I wrote introducing methods of skinning Flash MX 2004 components was published on DevNet. In the article I detail different basic methods of skinning components that involve both using the library or code as well as discuss that pluses and minuses of each. I know there has been a lot of discussion and interest on the subject and hope you find this article helpful.
You can find the article here
I’ll be in NYC for FlashForward towards the end of the week this week. I will be in town from thursday afternoon till saturday and will only be attending the conference on Friday. I’m really looking forward to Jared’s session, it’s his first time speaking and am sure it will be very intersting.
Also I have been too busy to keep up with what friends will be attending so drop me a line sometime this week so we can meet up.
IÂ’m posting this here in case anyone runs into a similar issue. In a recent application we built (All V2 based of course) we got a bug which turned out to be much harder to track down than initially anticipated.
Essentially what would happen is if a user clicked the up or down arrows on a scrollbar the player would stop executing any more code because of an infinite loop. After spending a lot of hours I tracked it down to an issue with the user clicking a ScrollBar’s up/down arrows which would in turn call the scrollIt() function inside of the ScrollBar class and somehow an infinite loop would occur (The ScrollBar in use was part of a ScrollPane). At first I tried to comment out the code inside of the scrollIt() function with no luck, then I tried just not calling scrollIt() which worked but didnÂ’t really help, I even tried re-writing some of the code of the ScrollBar class and also had no luck. At the end I ended up copying the scrollIt() functionÂ’s code into a new function called scrollIt2() and calling that instead when the user clicks up/down and that worked. Why it worked I have no idea, I spent a few more hours after fixing it trying to narrow it down and couldnÂ’t find any logical reason for the bug and had to move on.
I’ll go back and look at it one day when I have some more free time and isolate the issue.
An article I wrote was published today on ultrashock.com. The article introduces the V2 component architecture and discusses UIObject/UIComponent.
The Article Covers:
You can find it here.
I have made some minor changed to Flash Tray Tools. A lot of the requests received didn’t make it into this one. I’m hoping to add more features sometime next month. For now here are the additions
The installation process is a bit different than before. If you are upgrading delete the previous version and follow the instruction in the readme.txt