On 30 Jun, 2004, at 02:24 PM, Brad Beyenhof wrote:
I know it's been posted here before, but if someone who has encountered these bugs can send me (or even post again) their steps and system specs I'll try to make it happen and then send in a more concrete bug request.
-- Brad Beyenhof [EMAIL PROTECTED] http://augmentedfourth.blogspot.com
Hi Brad,
Reproducing the Text Block bug in Fin2004 is easy:
1) Open a bunch of documents generated from the same parent file -- such as a complete set of orchestra parts, or big band parts, etc. They should all be set to Page View.
2) Change one text block in one of the documents -- for instance, change the staff name header in the upper-left corner of one of the parts.
3) Cycle through all of the other documents, hitting command-D to redraw the screen after you switch. [Also, the changes don't always affect Page 1 -- you will have to look at every page of every document.]
4) If you have gone through the entire set of documents and found no unwanted changes, repeat steps (2) and (3) with some other text block in some other open document until the bug occurs.
You may also need to have "Autosave" enabled in order to be able to reproduce the bug (I'm working on confirming this). But if you're trying to reproduce the bug, I recommend setting Finale to Autosave every minute.
It should take you less than five minutes to reproduce the bug this way. This works on my system 100% of the time within five minutes. I am -- so far -- unable to figure out why some text block modifications bleed and some don't, or predict exactly when the bleed will happen. But I can always make it happen sooner or later.
- Darcy
----- [EMAIL PROTECTED] Brooklyn, NY
On Wednesday, June 30, 2004, at 11:02 AM, Christopher BJ Smith wrote:At 1:36 PM -0400 6/30/04, Darcy James Argue wrote:
Here's the original exchange again. Brad wrote:
To Whom it May Concern:
I wish to add my vote to the fixing of the most egregious Finale bug
I've ever heard of. The spontaneous changing of text blocks in open
documents, and in some cases the complete replacement of their
contents, is horrible!
(Snip)
Brad never said anything about the file-overwrite bug.
Looks to me that when Brad said "Complete replacement of their contents" he was referring to the files' contents, not the text blocks' contents. But the phrasing WAS ambiguous.
Yeah, I kinda meant the whole files' contents, but I agree upon rereading that it was pretty ambiguous. However, since I've never specifically encountered either of these bugs in my own experience, I can't see how I could have been much clearer.
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
