Chris Cannam wrote: > As to how best to use all this, my gut feel is that we should > probably work to make the refresh status code do what we need, > in cases where it doesn't now. This mostly means enhancing the > Composition to use a dedicated RefreshStatus object that can > actually describe things like segments added and removed rather > than just noting that "something happened".
I thought this over a bit more, and decided that a reasonable structure for describing general changes in the Composition really is too complicated. Given that most clients will only care about some sorts of changes (Segments added or removed, for example), we probably would be better off having the client make those queries and test just those things it cares about. I can take a look at that with the chord-name ruler and the segment mapper. It may be that the better way to simplify things is to provide a base class that knows how to look up certain sorts of data following a refresh-status update (for example, to keep a list of segments in the composition up-to-date) rather than to try to encapsulate all that information in the RefreshStatus itself. Chris ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
