Joseph Labrecque

I’m using AIR integration with Flex Builder 3 to contain and package an AS2 SWF which was originally using Screenweaver for deployment to a standalone app.

The problem I’ve noticed is that I have two areas into which each are being drawn from another MC using BitmapData.draw() which work just great in Flash CS3 when testing, but when deploying the AIR app using Flex 3, only the first BitmapData object is actually drawn on the stage. The other is totally blank.

[IMAGE MISSING!]
An example of this is above. Both windows should have the same image displayed at this point. I’m drawing out the rightmost image first- so the left image never gets drawn.

If I reverse the order in which they are drawn- the first one to invoke draw() is always the one that gets drawn.. very strange. Is this a known bug? Granted, it may have to do with my wrapping an AS2 app within an AS3 wrapper… but it’s really kinda weird nevertheless.

I’ve filed it as a bug with Adobe in any case.

CamStudio 2.5 is a screen recording application I’ve been using to author screencasts for the online courses I teach. These types of tutorials are really useful when teaching new users how to go about building things in Flash. It includes the option to output in FLV as well- so that is just perfect.

I kind of missed the release of this by a week or two. For some time, the website wasn’t updated and I had thought the project abandoned. Glad I was wrong- apparently this is considered a beta because 2.6 is on the horizon. Strange reasoning for a beta- but I can understand the need to release something… but having “2.5 beta” followed by a “2.5″ release makes more sense, in my opinion. I suppose they are only names.

I’ve posted before about some troubles I had with the previous versions of CamStudio getting the AVI output processed correctly in Premiere. I haven’t had the chance to try out this new version yet but it apparently works on Windows Vista and includes some expanded windowing options.

I’m a big fan of the project and very happy to see things moving forward.

I’m working on a rather large AS3 project through Fractured Vision Media which relies on the flash.system.fscommand package to properly transmit data from the application to its container layer. Unfortunately, we’ve come across a bug in which FSCommand calls are ignored! Through some quick research (e.g. Google) it was discovered that more than a few others have come across this problem as well.

The workaround for now is to be sure you are generating unique argument strings to pass through the FSCommand. This could involve changing the case of different characters in your argument string or appending a unique ID bassed off of something like the current time.

Does anyone know the status of this bug? Will it be patched in “Moviestar”? Seems pretty major to me…