Here we go. From http://www.macintouch.com/m8tips.html: "Finder 8.0 handles AppleEvents by suspending them and handling them in separate threads whereas Finder 7.5.6 handled AppleEvents immediately. The net result of this change is that AppleEvents sent to the Finder from within the Finder's process will immediately timeout (as per Inside Macintosh:Interapplication Communication) and finish completion when the thread completes. The Finder itself is not effected by this change but some third-party products (extensions & control panels) which send the Finder events from within its own process are effected. We are working with the third-parties to help them rev to work correctly but your readers might want to know that there are likely to be incompatibilities for awhile to come. Also, AppleScripts run from a script menu in the Finder's context must be revised to handle the new behavior. Since there are a considerable number of such scripts, it seems likely to me that full compliance will be a bit longer in coming for AppleScript writers than for the extension writers. Developers should expect incompatible extensions or scripts to fail with an error of -1712 (errAETimeout). A well written extension or script will not crash as a result but may return obscure error messages like 'The Finder cannot be found or is not running.' Again, this difference will not effect everybody, but will effect those users who use certain utilities which try to be closely integrated with the Finder or who use a Scripts menu in the Finder." I don't know whether or not MacPerl and AppleEvents.pm will be affected ... -- Chris Nandor pudge@pobox.com http://pudge.net/ %PGPKey=('B76E72AD',[1024,'0824 090B CE73 CA10 1FF7 7F13 8180 B6B6']) ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch