Hi Allen, Your request for suggestions on defaults gives me a chance to hop on a soap box for my main wish-list item.
You seem to be thinking in terms of improving the hard-wired defaults. What I'd like is a "style" mechanism that lets a user develop a set of defaults. You probably just said "we've got that with templates". No. What I mean by a "style" mechanism is one that lets you specify a style after-the-fact. Something like the "Cascading Style Sheets" or XSLT in HTML. E.g. I've got a library of over a hundred songs in Finale, and every so often I think up a way to make them more readable. E.g. I recently switched to Jazz Font, and that was a multi-week painful process. With a style mechanism it should take an hour or two to develop and test the new style, then an over-nite run to apply it to 100 files. Another example, I recently realized I should leave wider margins on the right, for two-sided printing (and 3-hole punches). I would think that after-the-fact style changes would be a common need. I'm currently dealing with a publisher who has all sorts of requests for character fonts, spacing, etc, that will be a big hassle to do a document-at-a-time. Warning: this is the sort of mechanism that programmers will commonly say "can't be done", but in fact turns out not to be a big deal. Thanks for asking, Phil Shaw - [EMAIL PROTECTED] - http://okshaw.com _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://mail.shsu.edu/mailman/listinfo/finale
