Re: [Finale] Text Block Bug Enigma Solved!
Darcy James Argue wrote: [snip] The workaround, in the meanwhile, is to turn off autosave. It should (knock on wood) now be safe to go back to working on multiple simultaneous documents in MacFin (provided you remember to save manually). I'm glad they've isolated the cause and can thus (it is to be hoped) solve it. In the meantime, knowing you can get around it by turning off AutoSave is a great benefit. I'll be that others who haven't been able to recreate your problem simply had Autosave turned off and thus couldn't reproduce the problem. I always turn off autosave immediately when I install any new application, preferring to save the file where and when I want. Congratulations on perservering to get at least official recognition of the problem, which is the all-important first step to a solution. -- David H. Bailey [EMAIL PROTECTED] ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
On 22.07.2004 12:41 Uhr, dhbailey wrote I always turn off autosave immediately when I install any new application, preferring to save the file where and when I want. And now, with OS X and Fin2k4, we Mac Users can actually turn it off, too. In OS 9 the whole thing just wasn't stable enough... Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
On 7/22/2004 12:41 PM, dhbailey wrote: [snip] I'll be that others who haven't been able to recreate your problem simply had Autosave turned off and thus couldn't reproduce the problem. I always turn off autosave immediately when I install any new application, preferring to save the file where and when I want. I was one of the people that were able to confirm the existence of this bug, and like you I always have Autosave turned OFF. Congratulations on perservering to get at least official recognition of the problem, which is the all-important first step to a solution. Hear, hear! ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
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
Re: [Finale] Text Block Bug Enigma Solved?
On 7/22/2004 5:25 PM, Brad Beyenhof wrote: 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. Erm, I always have Autosave OFF, and I can't remember Darcy asking me to switch it on. I've checked his instructions that came with the file. 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. Agreed. That's exactly why I responded. Barbara ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
Hi Johannes, I wish that were the case on my machine, but Finale is still relatively crashy. I just yesterday had to do a complete HD wipe and repartition, and so I'm taking the opportunity to reinstall everything from scratch -- a serious PITA, but perhaps with this absolutely pristine Panther 10.3.4 installation, I'll start getting the stability everyone else is raving about. Meanwhile, I just have to get into the habit of hitting cmd-S regularly. Cheers, - Darcy - [EMAIL PROTECTED] Brooklyn, NY On 22 Jul 2004, at 08:32 AM, Johannes Gebauer wrote: On 22.07.2004 12:41 Uhr, dhbailey wrote I always turn off autosave immediately when I install any new application, preferring to save the file where and when I want. And now, with OS X and Fin2k4, we Mac Users can actually turn it off, too. In OS 9 the whole thing just wasn't stable enough... Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
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
Re: [Finale] Text Block Bug Enigma Solved!
On 22.07.2004 19:59 Uhr, Darcy James Argue wrote 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. I am pretty sure it is a Mac-only bug, simply because the way Autosave works in OS X has changed in OS X. Or did you say you could reproduce the same bug in 2k3? I can't remember. Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
While we are on about Autosave, I really hope MakeMusic is going to change the general autosave behaviour under OS X as well. It's blXXdy annoying that the autosave message comes up on top of _everything_ even when Finale is far in the background. It's even more annoying when you have several large files open while this happens. And it is indefinitely more annoying when one of those files hasn't been saved yet: Finale brings up a File Saving dialog in front of everything, and occasionally it looses focus. When that happens I have not yet found a way to revive it and had to hard-quit Finale. (Another bug I guess.) I would also prefer it if Finale only saved _once_ while in the background, and not save every x minutes if Finale hasn't been touched in the meantime. It's ok while you are working with it, but not when I am typing my email. In OS 9, as far as I remember, Finale would only autosave while in the foreground. This did mean it quite frequently autosaved as soon as it was brought back in front, but I'd much rather have that behaviour than the stupidity it displays at the moment. And ideally I would like autsaves to happen completely in the background, so that I don't notice them at all. I really don't need to be told. Johannes -- http://www.musikmanufaktur.com http://www.camerata-berolinensis.de ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
On 22 Jul 2004 at 13:59, Darcy James Argue wrote: 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. It may be so, but when I encountered file overwrite problems on WinFin (can't remember if it was Finale 2K3 or 97), I didn't have AutoSave turned (philosophically, I don't believe in AutoSave). Lately, with all the problems I've been having with blank notation measures causing Finale to crash (I now have a second file with two different measures that when the leftmost measure in scroll view cause Finale to crash), I've turned it on. Up until recently, Finale has been extremely reliable for me (except for the old days when clicking on a blank in the tool palette caused it to crash -- but that was WinFin2.01!). -- David W. Fentonhttp://www.bway.net/~dfenton David Fenton Associateshttp://www.bway.net/~dfassoc ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
On 22 Jul 2004, at 02:37 PM, Johannes Gebauer wrote: While we are on about Autosave, I really hope MakeMusic is going to change the general autosave behaviour under OS X as well. It's blXXdy annoying that the autosave message comes up on top of _everything_ even when Finale is far in the background. It's even more annoying when you have several large files open while this happens. And it is indefinitely more annoying when one of those files hasn't been saved yet: Finale brings up a File Saving dialog in front of everything, and occasionally it looses focus. When that happens I have not yet found a way to revive it and had to hard-quit Finale. (Another bug I guess.) Yes -- the standard OS X behavior here would be for Finale's icon to bounce in the Dock, indicating that it needs your attention, but without grabbing focus from the currently active app. I know some people find the Dock bounce annoying, but at least then Finale would be annoying in a *Standard Way*. - Darcy - [EMAIL PROTECTED] Brooklyn, NY ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
On 22 Jul 2004, at 02:37 PM, Johannes Gebauer wrote: On 22.07.2004 19:59 Uhr, Darcy James Argue wrote 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. I am pretty sure it is a Mac-only bug, simply because the way Autosave works in OS X has changed in OS X. Or did you say you could reproduce the same bug in 2k3? I can't remember. Hi Johannes, Yes, I can reproduce in Fin2003 and Fin2002. - Darcy - [EMAIL PROTECTED] Brooklyn, NY ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
All-- This text block bug only happens on Mac... Allen ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Text Block Bug Enigma Solved!
Barbara Touburg wrote: I was one of the people that were able to confirm the existence of this bug, and like you I always have Autosave turned OFF. I have a hunch that the bug may not be dependent upon the state of the autosave feature. I suspect based upon my recollections of what happened when I was experiencing this behavior, that if one follows the procedure given in the message to Darcy, but with autosave inactivated and does a manual save at the point where the procedure speaks of waiting for Autosave, that the bug would also occur. HOWEVER, it's been a while since I experienced the bug personally, and I may be wrong about it. ns ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
