In a message dated 12/27/06 7:30:10 PM, [EMAIL PROTECTED] writes:
> The problem is that things don't work the way one might imagine if > you leave that "Break Multi-measure Rest" box unchecked. If you have > a 6 m. rest with an expression attached to the last measure, the > program only accommodates (shows) expressions attached to the first > measure of the mm rest, so anything at the end does not show. There > are workarounds, but they seem kludgy and fussy to me - requiring > multiple operations. I was wondering if anyone had come up with > anything elegant. > > Maybe it's one of those things that is not easily solved, but I been > surprised by my own blindness and the insights of others in the past, > so I have reason to hope. > > Chuck > Hi Chuck - I know what you mean and feel your pain. Remember the days when there really weren't options to avoid having expressions swallowed up by mm rests? Regarding your issue - I always pay close attention when there are roadmap instructions like "to Coda", etc. so they make it into the parts regardless of the material. In your situation, I find it useful to attach the expression (btw - if it was repeat text, I think it would split out the MM rest anyway) to the measure FOLLOWING the actual "to coda" jump (which is never part of a MM rest). The only time this doesn't work right is if there is a page break at that spot. This way it doesn't interfere with the MM rest and never gets buried. You can set the text positioning to right align on the left barline and it even places it properly (mostly). _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
