There’s an issue with the Proxy and XML classes when you use the [] syntax to execute methods.

For example, this is the working behaviour:

var g:Function = myProxy.go; // calls getProperty on the Proxy subclass
myProxy.go(); // calls callProperty on the Proxy subclass

This is the non-working behaviour:

var g:Function = myProxy['go']; // calls getProperty on the Proxy subclass
myProxy['go'](); // calls _getProperty_ on the Proxy subclass

In the second example the second line calls getProperty. So why is that a big deal? Two things: first, it’s not consistent with non-[] syntax, and second, it calls getProperty so you don’t know that the user is actually calling a method.

This was reported to Adobe on JIRA (Calling a method on a subclass of proxy dynamically invokes getProperty rather than callProperty) and after months of inactivity it was finally concluded that this is not a bug. Why? Here’s the example that was given:
(more…)

Having problems with getURL/navigateToURL or fscommand?

Using a getURL queue system because of a “bug in IE”?

Check this out:
FSCommand and getURL Bug in Flash Player 9

This will become more and more an issue with more and more people buying Flash CS3. In Flash CS3 you have the option to publish your AS1/AS2 projects for Flash Player 9 to take advantage of some of its features. If you do that, and your project uses getURL or fscommand, then it will be succeptible to this bug.

If you target Flash Player 8 in Flash CS3 you’ll be fine. The problem is when the player detects your SWF as being published for Flash Player 9 (AS1/AS2/AS3).

SWF Studio 3.4 has been released!

3.4 was in beta for a while and has now been officially released. This new version fixes the big issues people had with V3, including the MSVCR80.dll issues. And of course the big one is full Vista support. 3.4 runs on all Vista flavours and has Vista icon support, as well as the ability to include a manifest file so you can work with Vista’s UAC feature.

A quick run-down of the new features:

• run SWF Studio IDE/applications on all versions of Windows Vista
• increased stability
• support for Vista icons
• full Unicode support in plugins
• .NET plugin support and SDK - write plugins with C# and VB.NET
• includes Flash Player 9
• more … (release notes)

You may have noticed that although Flash Player 9 is included in your 3.4 applications, AS3 support is not mentioned. AS3 support is coming in a future version of SWF Studio. In order to increase stability and get proper Vista support a core technology was modified. We felt it would be too much of a change to have that modification AND AS3 support in one release. We wanted to release a MORE stable product, not chase after features at the expense of stability. 3.4 was in beta for a while and we feel as though we’ve released a solid product.

AS3 support isn’t that far away since most of the work was already done - we just put the remaining work on hiatus until 3.4 was tested and released. Another beta will start in the coming weeks with AS3 support. The AS3 beta will be closed so send your registration info to beta at northcode.com if you want in on it.

There’s a new look to the site. The home page gets to the point and the info on the other pages is broken up better so you can find everything a lot easier. It’s still a work in progress. We’ve talked about focusing on certain features every <insert time frame here> for new users and users that just haven’t used that feature yet. As well as a blog that will let us discuss SWF Studio and other related matters. Stay tuned …

Try it out, then come back to this site and click on the link near the top-right: Buy SWF Studio for 10% off!

I know a lot of people have moved on to Flex 2 and Flash CS3 but there are many people that are still forced to use Flash 8 and earlier due to a variety of circumstances. I am one such individual.

In developing an app for a client I found an issue with V2 List and Tree that I had seen before but never really bothered with. Previously this issue was simply an annoyance. But in this current app the lnf needs to have a solid 1 pixel border around instances of the List and the Tree components.

The issue is a 1 pixel “extra” space between the left border and list items. No matter what you set the borderStyle to be the extra pixel is always there. This becomes very obvious when setting the borderStyle to none or solid and hovering over an item.
(more…)