All, > Whose problem is it? > Did Apple do something in their code that "broke" the > original function > or did MM not use the correct function in the first place and > have been > "caught out"? > > I hope someone fixes it real soon, cus it a PITA
Ok, I've got my fire-suit on 'cause I fear the response to what I'm about to say but here goes... It's our problem 'cause the bug is in our app. So we'll fix this in the next release. Panther is not an officially supported platform for Director MX and as will all software products you must adopt a "use at your own risk" policy any time you upgrade an OS after a product has shipped. We worked with Apple during our porting effort to try an ensure that we followed their guidelines, I don't know whether this particular problem is due to a change in the OS or as you put it, us getting "caught out" with errors in our code. Sorry folks, but Macromedia will not be providing an update for Director MX to resolve issues with Panther as it's not a supported OS for that version. The next release will obviously include Panther support and fixes for issues like this one. I thought it worth stepping out and explicitly addressing the questions of "will there be an update for this?", even if the answer might not be popular. <putting the fire-suit hood on> Cheers, Tom Higgins Product Specialist - Director Team Macromedia ... [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!]
