When typing the " ` " (option-tilde), as in più mosso or " ´ " (option-e), as in the formal name of treble clef 2nd line G (g´) while in Finale v25, Mac OS Mojave, the program "unexpectedly" quits. This happens in the lyric and create expression windows. It seems fine in the Score Manager when typing an artist's name like "Renée". Has anyone else encountered this?
Thanks for your input.
We don't have enough information.
https://makemusic.zendesk.com/hc/en-us/community/posts/215729367-General-Discussion-House-Rules
In your case, knowing the version of Finale, 25.what?, Mojave (25.5 update was two days ago) and the font are good places to start.
In the mean time, I recommend performing a Safe Boot by shutting down and starting with the Shift key held down—log into your User account when prompted, then reboot when all your desktop icons have been rebuilt. This restores caches to default and rebuilds your paths. I've seen this fix a number of annoying issues in Mojave.
I'm still on High Sierra, but here are a couple of suggestions:
For the più, you can use the long press: just hold down the u key until a flyout appears with a number of options. Tap the number of the one you want.
As for the ´ following the g, try Text > Inset > Symbol, and find it in the next screen. In Times New Roman, it's number 714. If you want that accent on a vowel, again, use the long press.
You should also send it in to tech support, so they can log it as a problem. And then ignore it, probably...
What MikeR says. If the long press works but option keys do not, there are a number of possible causes. If the long press also causes you grief, time to look harder.
Any chance you have a 3rd party macro utility such as QuickKeys running? Have you mapped any key combinations of other apps? Sometimes, these can have unintended consequences in Finale. A crash log or Console trace should find them.
If this is recent, an app upgrade or install may have caused this. Try reinstalling Finale and rebooting,
Otherwise, my earlier suggestion is stil a good one. Do a Safe Boot, then shut down and reboot normally. If the problem is a corrupted path or cache, this cleans up both.
Please sign in to leave a comment.
6 comments
Date Votes