On Jan 22, 2005, at 7:07 AM, Jari Williamsson wrote:
Perhaps it would be more productive if the Mac users who repeatedly experience this problem analyzed (in detail) what they did _prior_ to when the problem occured that is _different_ to what they do when it does _not_ happen. It can be any silly little thing along the way that matters here.
Oh, we've tried! Here are some things that have cropped up, confirmed and unconfirmed by others:
open text block in one of the open files (not confirmed)
text blocks in two different files have the same ID (how we might control or even identify this is beyond me)
the file comes from a previous version of Finale (100% true for every instance of the bug in my case, but I often work on old files with NO bug striking at all.)
I stop what I am doing with all the presently open files, open a different file in Finder by double-clicking on it, edit something (usually a text block) and save that file. When I go back to the other open files, the bug has struck. (this does NOT cause the bug even 5% of the time, but doing things like this seem to be risky behaviour.)
The concept of the system being stressed, or Finale having been running for a long time and building up a whole crop of temp files, is new to me, but entirely possible. I have never had the bug strike on a freshly-booted machine, or when Finale has been newly opened. The first time the bug occurred Finale crashed soon afterwards, and I have always quit and restarted Finale immediately after noticing the bug every time since.
Christopher
_______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
