The last thing I did before switching out of Finale *was* printing to PDF. However, the PDF had completed long before Finale crashed.
That would seem to concur with my guess: There's something like a SPOOL_JOB_DONE signal (the modal dialog disappears) which tells Finale it can resume being in a non-blocking UI state. However there's also a PRINT_JOB_DONE signal (PDF done). I'd bet it came back after you had switched but assumed the Finale state from SPOOL_JOB_DONE rather than determining it dynamically. Further, there's the possibility that Finale might have been tracking the Nav Manager dialog involved. All very complicated IMO because the Finale engineers have also had to deal with behavior changes in the Print Manager APIs (CUPS, Print Utility vs Print Center e.g.).
Philip Aker http://www.aker.ca
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
