At 10:48 PM 08/20/2004, Noel Stoutenburg wrote:
>WRT the latter point, the fundamental issue related to this is one that
>Dr. Patterson and I both alluded to:  lead time.  We don't know when the
>bug was discovered.

Yes, this is very true. My assumption is that since I found the bug so quickly, at least one of the beta testers probably did as well. But I have no proof of that.

>With respect to the former, IMO,. if the bug only occurs when the tuplet
>begins with a rest, then it fails to rise to my own definition of
>"serious" or "basic".  To me, a serious bug is one which causes the
>computer to hang up, and lose all data, or fail to start at all.

Well, I certainly agree that that kind of bug is more serious, but...

> A bug
>which affects only the instance when the tuplet begins with an eighth
>rest merely rises to the level of "irritating", or "annoying", and
>should not inhibit the shipment process.

...I think I was using the words more relatively. The idea of enhanced tuplets is to make it unnecessary (or at least far less necessary) to manually edit tuplets. IMO, one of the worst current tuplet issues occurs when the tuplet begins with a rest: the bracket is flat and in the staff, often colliding with notes. Enhanced tuplets solves this positioning problem but makes it necessary to manually edit the tuplet anyway, to get the number positioning correct. So to me this bug is "basic" relative to its feature, since it renders that feature significantly less useful. Similarly, the other bug discussed recently about Speedy in Page View is basic because it renders *that* feature useless.

>BTW, what happens if, instead of an eighth note rest, one creates the
>tuplet with two sixteenth note rests at the beginning, and goes back and
>deletes one of the sixteenth notes, and changes the remaining one to an
>eighth?

This is a highly impractical sequence in Speedy Entry (i.e., not at all speedy) -- and it gives the same result.

I don't want to beat this issue to death, if I haven't already. I agree that this is no worse than many other Finale bugs, but I find the particular combination of factors associated with it quite galling. Your mileage may vary.

Aaron.

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

Reply via email to