- - -
As a developer I use both multiple monitors and OS X Spaces when working with the Flash IDE. While I don't usually code within Flash, but rather FDT, I do like to have the actions and output panels open on my second monitor while working in Flash. This allows me to free up space within the main Flash work area and requires much less collapsing and expanding of panels while working throughout the day.
I had come across a bug in Flash CS3 a while back where OS X Spaces would cause the Flash IDE windowing system to become completely unusable after switching between spaces a few times. Sadly, this bug is still present in Flash CS4 - and even more prevalent. So, I decided to email Adobe to see if the issue could be resolved. In the process I took a screencast of my desktop to help them diagnose the problem. Below is what I have sent them:
The issue in question with Flash CS4 (and possibly other CS4 apps) can be found in OS X 10.5 (I'm specifically running 10.5.5) when using two or more "spaces". Additionally, one of the panels needs to be in its own window -- for instance the actions panel should not be docked within the application interface -- and also placed on a second monitor/display from the application.
In the video below I am recording my main display while my secondary display is not visible, and on that second monitor I have an undocked actions panel. The video shows me switching back and forth between two OS X spaces - one with FDT open, the second with Flash CS4 open. As you can see, switching back and forth between the spaces can cause the Flash CS4 interface to become "detached" from itself. This ends up being a very frustrating issue because there isn't a lot that users can do to solve the problem, and any solutions I have found don't seem to work consistently. In fact, the only fix I have found is the bring the undocked windows (in this case the actions/output panel) back onto the main monitor, overlapping the Flash IDE.
Here is the video, re-sized to fit within my blog:
You can also download the original screencast as a Quicktime .MOV here, which is much larger and clear.
Sadly, no fix yet, but let's hope if enough people also note the issue it will be fixed in the next update.