Hi Brad,
The files I sent out to you and Barbara, etc., did *not* require you to turn on autosave to see the erratic behavior, because they had already been corrupted by the bug. What's new is that Coda have figured out how to reproduce the bug from scratch, whereas the best I could do was show them (and you) some particularly messed-up files and ask everyone to confirm that the weirdness was not a product of my own imagination, and not machine-specific, either.
I asked some people to try to confirm this bug from scratch, using their own documents, and I asked them to set autosave to "every minute", and unfortunately no one was able to do it. But the key variable that I didn't understand is that you have to have a Text Block open (i.e., with a flashing cursor) when Finale autosaves. This is why this bug kept biting me personally all the bloody time in my own work (because I had Autosave set to a short interval and I often need to edit text blocks when preparing parts), but seemed impossible for anyone else to reproduce under controlled conditions -- because they would just change one text block, *close it*, wait for the autosave, cycle through the active windows, notice nothing had changed, and conclude I was barking mad.
[Joke, joke -- my *sincerest* thanks to everyone who took the time to try to reproduce this bug, and to those who petitioned Coda to take the problem seriously -- if it weren't for you, we would all still be in the dark and the problem would have gone uncorrected. I only wish I had been able to give you better instructions.]
Along those lines, I'd still like for a Windows user to try those steps I quoted in the first message, so we know if this is a Mac bug or a general Finale bug.
You are right that the files I sent, with the expression turning into the enclosed "I" character in JazzFont and the linked Text Block and Expression, seems like they might be examples a different problem. But I think it's really just a particularly bizarre symptom of the same problem, where Finale's autosave causes serious problems with pretty much any text (text blocks, expressions, staff names) that is being edited when the autosave takes place.
Of course, this is only when multiple documents are open. Autosave should still be safe for people who never have multiple documents open.
I also think the file-overwrite bug is probably related to this buggy autosave implementation. I know Coda is looking into that as well, so hopefully everything will be fixed at the same time.
- Darcy ----- [EMAIL PROTECTED] Brooklyn, NY
On 22 Jul 2004, at 11:25 AM, Brad Beyenhof wrote:
On Thu, 22 Jul 2004 05:54:41 -0400, Darcy James Argue <[EMAIL PROTECTED]> wrote:One of the smart, smart cookies at Coda sent this to me yesterday:[snip]They got it! Brilliant! My faith in Coda is restored![snip]I'm *so* happy this has been isolated -- hopefully, now, it won't be too difficult to fix.
Darcy: Awesome! However, does this have anything to do with the "enclosed 'I' character" thing you ran across in Text Expressions? I got that one to bite me in your test file, but is that going to be covered by the bugfix for the "multiple file" bug? It seems a bit different in nature to me.
Barbara: Just checking... you did turn Autosave ON when you confirmed this bug, right? The way you phrase it seems ambiguous to me, and if you got the bug to bite you with Autosave off then the Coda estimation of the problem is incomplete at best.
List at large: I'm happy that Coda has recognized this bug, and I'm not trying to poke holes in people's happiness just for the fun of it. I just want to make sure we get all of our bases covered and we don't end up with a half-assed bugfix that doesn't fully patch the hole.
-- Brad Beyenhof [EMAIL PROTECTED] http://augmentedfourth.blogspot.com _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
