[Finale] 2K7 question

2009-04-04 Thread Lawrence David Eden

I recently moved from 2K4c to 2K7 (Mac)

When I extract parts in 2K7, I do not see the staff name on the extracted part.
For example:  Trumpet 1 in Bb

Part names on the parts was the default in 2K4.  How do I make this 
the default behavior in 2K7?

___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] 2K7 question

2009-04-04 Thread Christopher Smith
Yeah, they claim the part extraction process is identical in 2007,  
but it isn't quite. If you created a score with the Setup Wizard in  
2007, then all the parts are automatically created. For older files,  
you have to create them with a command. Go to DocumentManage  
Parts... and click Generate Parts. This will create a part for each  
staff or group in the score, with the same name. It will also  
overwrite any other parts you may have had generated before. You can  
change the name of the PART afterwards by clicking Edit Part  
Definition. Careful, because one time I changed the first trumpet  
STAFF name to Eb trumpet, but neglected to change the PART name  
afterward, and he ended up getting a part in Eb but called Bb, which  
didn't work out too well.


Christopher


On Apr 4, 2009, at 11:48 AM, Lawrence David Eden wrote:


I recently moved from 2K4c to 2K7 (Mac)

When I extract parts in 2K7, I do not see the staff name on the  
extracted part.

For example:  Trumpet 1 in Bb

Part names on the parts was the default in 2K4.  How do I make this  
the default behavior in 2K7?

___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


Re: [Finale] 2K7 question

2009-04-04 Thread Aaron Sherber

On 4/4/2009 11:48 AM, Lawrence David Eden wrote:

When I extract parts in 2K7, I do not see the staff name on the extracted part.
For example:  Trumpet 1 in Bb


Christopher Smith gave you some answers having to do with linked parts, 
which were introduced in 2007. If you want to go the old-fashioned 
Extract Parts route, Finale will still generate linked parts 
automatically behind the scenes; an extracted part is just a linked part 
snapshot split out into its own file.


If you go through the Extract Parts dialog and you only see Score 
listed, you first need to click the Generate Parts button to get Finale 
to create the linked parts. You can then check off the parts you want 
and extract.


Now, to get back to your original question about part names. What you 
will need to do is first generate the linked parts. Then go to page view 
in your score and add a text box. In this text box, put in the text 
insert that says Part/Score Name. Now you want to make sure that this 
text box is hidden in the score (because a box that says Score isn't 
helpful) but displays in the parts. On Windows, I would hold down the 
Ctrl key, right click on the text box, and choose Hide. I don't know 
what the Mac equivalents are to Ctrl and right-clicking. The text box 
will now appear a light orange in the score (meaning unlinked and 
hidden) and regular orange in the part (meaning unlinked and showing).


If you create a new score through the setup, this should be taken care 
of for you automatically, since the default files that come with 2007 
include this text box.


Aaron.
___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale


[Finale] Some Microsoft Perspectives on Bug Fixing In Software

2009-04-04 Thread David W. Fenton
I just ran across these two articles from Microsoft employees about 
how the process of fixing bugs works:

Why doesn't Office just fix all of the bugs before they ship it?
http://tinyurl.com/5ou884 (which is this:
http://blogs.technet.com/office_sustained_engineering/archive/2008/12/
12/why-doesn-t-office-just-fix-all-of-the-bugs-before-they-ship-
it.aspx)

Saying goodbye to our intern leads to a reason why a bug did not 
get fixed in Office 97
http://tinyurl.com/c298e4
(which is this: 
http://blogs.msdn.com/johnguin/archive/2008/08/21/saying-goodbye-to-
our-intern-leads-to-a-reason-why-a-bug-did-not-get-fixed-in-office-
97.aspx)

The second one is particularly valuable in that it gives a rundown on 
why a fairly annoying bug would go unfixed when there is a simple 
workaround and it is going to be encountered by only a few users.

-- 
David W. Fentonhttp://dfenton.com
David Fenton Associates   http://dfenton.com/DFA/


___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale