I like to wait a little while before I upgrade software... I've had too many experiences with 'apocalyptic bustage.' After the first patch to Snow Leopard and Flashbuilder hitting beta 2 - I thought the waters were safe. Famous last words...

It turns out that there is a crazy display issue for Mac developers that causes external / secondary displays to fail when updating the code editing window; line numbers don't scroll, break points don't show up, imports go missing, and crazy errors don't coincide with what you see. Nice.

Adobe knows about it... and there are at least two bugs that outline the problem as well as a potential workaround. Is this an Apple problem? Is it an Adobe problem? ...or are the Eclipse folks to blame?

http://bugs.adobe.com/jira/browse/FB-23023
https://bugs.adobe.com/jira/browse/FB-23614

For anyone that might be tempted to say "it's just line numbers" remember that I said this issue touches break points, updating imports... pretty much anything that is dependent upon some kind of editor / code window refresh - things can get out of sync pretty quickly. Productivity... killed... can't breathe... Spock... please... vote for the previously mentioned issues in the Adobe bug-base.

http://forums.adobe.com/message/2271332

This would probably be a good time to embrace the fact that Carbon is on it's way out... and that Flashbuilder compatibility with Cocoa 32/64 bit Eclipse is becoming more and more important to us Mac folks. What say-ye Adobe-ites?

UPDATE: A solution is at hand! Here is patch that will fix this bug... for now.