Jonathan Smith wrote:
Oh no!
I was really hoping that this would have been improved in 2009. I have
2009 but haven't installed yet as I'm in the middle of a big project, I
was also going to wait for the first tech. upgrade based on my
experiences of previous upgrades.
I must start to use TG tools if it copies across the hairpins, something
I have never understood why the explode metatool never covered- I mean,
isn't it plainly obvious that 99% of users would want all expressions
etc to go with the explosion into the separate parts?
The ironic thing that is that if you choose to IMPLODE multi parts you
get multiple expressions and hairpins in the target part - again,
exactly what you don't want in this case, but it proves that they could
easily program these things in if a little thought was to go into it.
[snip]
While I agree with your assessment of the need for haripins
and expressions to copy when we explode one staff to
multiple staves and that we don't need multiple hairpins and
expressions when we implode, I have to say that your logic
about the developers' ability to program stuff doesn't hold up.
When you have multiple staves, each with their own hairpins
and expressions, those things get copied with the notes when
the notes get copied (along with the music from other
staves) onto a single staff when we Implode. The
programmers don't create those multiple instances, they're
already in the data.
When you explode, there is only a single instance of each
hairpin and expression, so to end up with one on each new
staff means that the developers need to create more
instances of those hairpins and expressions.
It's not that they did the programming when they shouldn't
have and they didn't do it when they should have, it's
simply a matter of the Implode and Explode functions copy
all the data available, plain and simple.
So the programmers will need to come up with a subroutine
which duplicates the hairpins and expressions to equal the
number of separate staves which will be created by the
Explode function.
Definitely needed, but I don't think it's an easy thing to do.
--
David H. Bailey
[EMAIL PROTECTED]
_______________________________________________
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale
