On 16 May 2004 at 12:29, Philip Aker wrote: > But to be fair, since it's generally acknowledged that Finale has > features the competition doesn't, it stands to reason that the sheer > number of object types supported in permutation and combination with > the variety of means they may be placed will increase the number of > calculations required by factorial leaps. That is part of the price > one pays for flexibility.
Why should those complications be exposed at the display level? Finale shouldn't repaint parts of the screen that have not been updated. It obviously isn't smart enough to tell the difference, so it repaints everything. So, the problem is *not* in the interface between Finale and the graphics subsystem -- it's in what Finale is telling the graphics subsystem to do in the first place. On the other hand, is anyone complaining about the loss of redraw interrupt on Windows? I don't think so -- I certainly don't see it as an issue that I'd worry about, since the screen redraw in WinFin2K3 is fast enough to be no big deal (and I'm not on up-to-date hardware -- I'm using a 1999 PC). -- 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
