On 08 Jun 2004, at 06:49 PM, Matthew Hindson Fastmail Account wrote:

- Sometimes, when autosave is activated, something happens meaning that it's
impossible to click on anything, necessitating a force-quit. It seems to
happen sporadically, though mostly when a piece hasn't been previously saved
before. Sort of makes Autosave undesirable if in fact what it forces you to
do is leave the application _without_ saving!

Yes, autosave in FinMac2004 is *very* buggy. It seems like most of the crashes and hangs I have are autosave-related. I don't know if it's *quite* worth turning it off -- because then you might accidentally lose hours of work instead of just five minutes or less -- but it is extremely frustrating. If you can trust yourself to remember to save manually every five minutes or so, by all means turn it off.


- In the Measure tool, clicking on the bottom handle in a note-spaced bar
gave no handles for editing the beat charts.

I've never seen this.

- Using the Selection Tool is now glacial in speed as compared to Finale
2002 OS9, particularly with actually selecting the object in the first
place.

God yes. The selection tool in MacFin2004 is practically useless.

- I found it very difficult to drag measure-attached expressions
horizontally for any distance. The mouse would get ahead of the expression
and I couldn't tell whether it was being dragged successfully or not.
Redrawing the screen would put the expression back where it started.

Haven't seen this.

- Some plugin actions (e.g. Add Cue Notes in TGTools) were much, much slower
than in 2002b OS9.

Yes. Turn off the message bar -- that helps a *lot*.

- The Cautionary Accidentals PI would put accidentals on repeated notes even
if "Don't Put on Repeated Notes" was checked.

I haven't noticed any changes in the Cautionary Accidentals PI from when it started as Cautionary Accidentals TG. It's still buggy in many areas, though I haven't generally had problems with "No Cautionaries on Repeated Notes." Do you have "Auto-Freeze Accidentals" turned on?


- Double-clicking on the title bar of plugin windows in TGTools caused a
Force-Quit, as did mistakenly double-clicking on a Finale plugin from the
Finder.

Not for me -- double-clicking the title bar to minimize the window works fine. Do you have some third-party windowshade utility installed?


Also, in OS X, personally I find it's easier to use command-M to minimize the window, instead of double-clicking on the title bar. However, for completely mysterious and idiotic reasons, Finale does not support this keyboard shortcut (which is supposed to be *UNIVERSAL* to *ALL OS X APPLICATIONS*, guys). Use iKey or QuicKeys to bind cmd-M to "Minimize Window" in Finale to regain that functionality.

I did miss many of the outstanding plugins available in Fin2002 under OS9,
including Jari's ones and Phillip's Classic Transposition and Text Editor.
Philip, are you planning to update any of these to OS X? Please say yes!
:-)

I think Philip is working on OS X versions of his plugins. Jari announced he was releasing the source code to his MacFin plugins in the hopes that someone else would update them for OS X. I don't know if anyone's taken him up on that offer yet -- I sure hope somebody does. It was great that Jari made them available for free for so long, but if someone else wants to update them and start charging for them, I'll gladly pay. That's far better than not having them available at all.


It's perhaps a little frustrating that I found all of these (possible) bugs
after just one day's intensive Finale 2004b use.

Yep.

Goodness knows what else
awaits.

Well, if you ever have more than one Finale document open at once, text blocks from the active document will start bleeding into the inactive documents, replacing other text blocks, expressions, staff names -- you name it, it will be overwritten. Also, the changes won't show up just by bringing an inactive document to the front -- you have to redraw the screen to see what a mess Finale's made of your doucment. It should take you less than an hour of making changes to text blocks with multiple simultaneous documents open to witness this problem for yourself.


The only foolproof solution is to never have multiple documents open at once. I realize that's not much of a solution, but for now it's the only safe way to work. If this makes you as angry as it makes me, please let Coda know. They're already aware of the bug and presumably trying to fix it, but the more people who complain, the higher priority Coda will put on finding a solution.

The other thing to watch out for is Finale changing the name of your file, causing it to overwrite an existing file, without telling you. This bug is relatively rare, but three people on the list have already fallen prey to it, and boy does it suck when it happens to you. Make sure you turn on "Make Backups When Saving Files." You'll need it.

To be fair, on the plus side, Finalescript is excellent, especially if you
don't have a Macro application, and bodes well for the future if its power
can be further extended.

I still haven't looked at Finalescript at all. It all seems kind of arcane and confusing. What are people using FinaleScript for?


- Darcy

-----

[EMAIL PROTECTED]
Brooklyn NY


_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to