>Could you list or briefly describe these other bugs as well?
The biggest one is that Flash corrupts high-ansi characters on the Mac. Pass a string to Flash with setVariable, and it can show up corrupted in the Flash sprite. Worse yet, it corrupts the original string in Director. This seems to happen most often setting a variable in a movie clip where the field isn't on the screen. E.g., a book that's open--set the title on the cover (which you can't see because it's open), then go to a Flash frame that shows the book closed, i.e., showing the text. High ansi characters may be corrupted. This isn't really a bug, but an impediment--each Flash sprite launches an instance of the Flash Asset Xtra, and that really chews up memory. If you do a goToFrame while the mouse is offstage, the Flash sprite will often not update. You can recreate this with a multi-frame Flash movie and a series of goToFrame's run from a timer. The Flash Asset Xtra will sometimes intercept an Alt-F4 on Windows and bail to the desktop, even if the sprite is set to "pass events always." We have a trap in our Lingo code for Alt-F4, but Director never sees it, especially with a large, active Flash sprite. Ok, there are four, and the one I just posted makes five. I have more logged on my machine at work, but since it's Good Friday, I'm at home. I'll check on Monday if you'd like to see more. Cordially, Kerry Thompson [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
