Hi Chuck and Mike,

While this won't solve the underlying issue you're both talking about, I 
thought it would be worth mentioning another input method that can work in 
these situations that doesn't require using the mouse (which you may already 
know about). The drag is that is requires memorizing the suffix's placement in 
the library - the number of the "box" that it occupies (assuming the suffix 
exists already, of course).

While in "Type into Score", you type the letter name of the root, followed by a 
colon, followed by the number of the "slot" from the library (e.g. my "add9" 
happens to be in slot 22, so if I type C:22 I get that symbol).

If you don't have too many suffixes that you need to do this way, it's not too 
cumbersome, although obviously it would be preferable to be able to just type 
as we do for the other ones.

Again, you probably know this already, but may not have had reason to use it in 
this context.

Doug


On Dec 17, 2012, at 10:26 AM, Chuck Israels wrote:

> I have a similar problem with sus4 suffixes.  I assumed that it was because 
> of the special keystrokes required to create the superscript text, key 
> combinations I don't have reason to remember after having created the 
> suffixes I need.  I always have to enter those suffixes by going into dialog 
> boxes and selecting them.  If there is an easy "Type Into Score" method for 
> this, I'd be grateful to know it too.
> 
> Chuck
> 
> 
> On Dec 17, 2012, at 9:02 AM, Mike Casteel <[email protected]> wrote:
> 
>> Hello all,
>> 
>> I have encountered a problem with Bill Duncan's ChordSuf font- namely the 
>> (addX) suffix (it is not recognized, even if it is already in my library 
>> when "typing into score"). I can create it easily if I enter it manually (in 
>> the chord definition dialog box) but if I "type into score" it will not 
>> work. Nor will it work if I create the suffix from scratch in the chord 
>> suffix editor window. In each of those cases, I get unwanted characters. I 
>> suppose this has something to do with Finale's Unicode font support?
>> 
>> Has anyone encountered this specific problem and is there a way around it?
>> 
>> Many thanks!
>> Mike Casteel
>> _______________________________________________
>> Finale mailing list
>> [email protected]
>> http://lists.shsu.edu/mailman/listinfo/finale
> 
> Chuck Israels
> 8831 SE 12th Ave.
> Portland, OR 97202-7097
> 
> land line: (503) 954-2107
> cell phone: (360) 201-3434
> 
> <www.chuckisraelsjazz.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

Reply via email to