Glissando Tool not producing a wavy line

General notation questions, including advanced notation, formatting, etc., go here.

Moderators: Peter Thomsen, miker

bill90125
Posts: 4
Joined: Tue Sep 25, 2012 6:56 pm
Finale Version: 2014.d
Operating System: Windows

Post by bill90125 » Tue Dec 29, 2015 7:13 pm

I have always used the glissando tool, with a wavy line between notes, without issue. All of a sudden, it is an arched dotted line over the two notes, which looks like another tool entirely. Tried old documents, creating new documents, it does the same thing on everything now.


bill90125
Posts: 4
Joined: Tue Sep 25, 2012 6:56 pm
Finale Version: 2014.d
Operating System: Windows

Post by bill90125 » Tue Dec 29, 2015 7:28 pm

Followup: I figured out that every tool in the Smart Palette is doing the same thing. Closing Finale and restarting it did nothing. However, rebooting the OS entirely and restarting Finale did restore the Smart Palette to it's original functions.

User avatar
Peter Thomsen
Posts: 6601
Joined: Fri Jul 25, 2003 6:47 pm
Finale Version: Finale v27.4
Operating System: Mac

Post by Peter Thomsen » Tue Dec 29, 2015 10:14 pm

It sounds like the (electronically) stuck key syndrome.
As you have found out, a reboot fixes the problem.

In the Smart Shape Tool you got a dashed curve.
The stuck key probably was the letter V key, since the letter V key is the default trigger key for the metatool to the Dashed Curve (sub-)Tool.
Mac OS X 12.6.9 (Monterey), Finale user since 1996

bill90125
Posts: 4
Joined: Tue Sep 25, 2012 6:56 pm
Finale Version: 2014.d
Operating System: Windows

Post by bill90125 » Thu Dec 31, 2015 4:52 pm

Is the stuck key a Finale problem, or a symptom of a hardware issue, because it happened again, and it's really annoying.

User avatar
miker
Posts: 5993
Joined: Fri Mar 13, 2009 4:28 pm
Finale Version: Finale 27.4
Operating System: Mac

Post by miker » Thu Dec 31, 2015 7:22 pm

It's a Finale problem, for several years and versions, on multiple platforms and operating system versions. However, nobody has ever been able to pinpoint the cause. Different folk experience different "stuck" keys, but they seem to be consistent for each user. And some people never see it.

Probably something buried deep in the legacy code, and will most likely never be fixed.

Send in a bug report.
Finale 27 | SmartScorePro 64
Mac OS 13.2.1 Ventura
Copyist for Barbershop Harmony Society

Post Reply