On 4 May 2004 at 0:12, Colin Broom wrote: > I keep coming across this issue that is frequent enough that I'm sure > it isn't me. > > Periodically I go to do something in Finale that involves a key > command (two recent examples are massmoving one bar to the next system > with the down arrow,or changing a duration in speedy) and I find that > the keyboard appears not to respond (that's how it seems anyway). At > first, I couldn't figure it out, but now I find if I simply press the > Alt key, it returns to normal and I am able to perform the task.
Well, the Alt key activates the menu bar, and Finale only recently (originally partly in WinFin97, then more completely in later versions) changed to behave like a normal Windows program in this regard, mostly I think, because Coda switched to using Microsoft development tools (this is where the MS-like toolbars came from, along with all the annoyances that brings with it, including the issue recently mentioned here on the list where doing things in Internet Options causes problems with your Finale toolbars). > Now, I'm sure it's not just me accidentally pressing the Alt key by > accident in the first instance, as I've never had this problem before > with any previous version of Finale, though I won't completely > discount it (it just seems a bit unlikely). Has anyone come across > anything like this in 2K4? Is it happening after you've used the keyboard to access something on a menu? If so, there might be something in the new Finale that's failing to release the focus from the menu bar back to the document context. I don't know why this kind of thing would be broken from one version to the next, but it's the kind of detail that can require a lot of attention on the part of the programmer to keep from happening. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
