Just doin’ my part. (French and German also available)
<a href=”http://www.macromedia.com/support/flash/downloads.html”>Downloads</a>
<a href=”http://download.macromedia.com/pub/flash/updates/mx2004/update_fmx_2004.exe”>English Updater EXE</a>
<a href=”http://www.macromedia.com/support/documentation/en/flash/releasenotes.html”>Release Notes</a>
My co-worker, <a href=”http://www.erikbianchi.com/”>Erik</a>, has brought up an interesting question: What’s Next? He’s specifically referring to the progression of programming. First came procedural, then came OOP, but what comes after that? Here’s what I think.
Read on…
I seem to be getting incorrect return values from JSAPI via MMExecute for the following Item object property on Compiled Clips:
– linkageExportForAS
The property determines whether or not the symbol in the library is exported for ActionScript (so you can use attachMovie using it via its linkage name). I’m getting a string of “undefined” returned, but all compiled clips that I can see are exported for ActionScript by default. The other properties, like “linkageExportForRS” work as expected; “undefined” if not capable of being checked, false if not checked. I’ve tested in my Window SWF and as regular JSAPI being run via the Command menu.
Is this a bug? Can anyone else confirm?
FINALLY, got DSL after a whole week without internet… I was gonna jump out my window tonight… and fall 2 feet on the grass, but anyway, no need for such dellusions of faux pau sympathies bequethed by the soft sod from Bermuda. Thank God for her majesty.
If you are making a window SWF and want to see it update without having to reboot Flash, what I’ve been doing is saving the FLA file in the Window SWF directory:
C:\Documents and Settings\warden\Local Settings\Application Data\Macromedia\Flash MX 2004\en\Configuration\WindowSWF
on my XP box.
I close the Window SWF after testing, publish the file after an update, and then re-open the Window. Works like a charm!