Guillaume Laurent wrote: > OK, that explains the problem : when loading a file, refresh() won't > be called.
Ah! >> No such thing. A repeating segment always ends at the >> composition's end marker time. > > Oh, I must be confusing things with loops, then. Probably so. >> Yes, it's certainly slower. > > Actually I'm more concerned by the complexity of the code required to > maintain the N copies whenever a change occurs. It's trivial, isn't it? At the moment we just rewrite the whole segment (don't we?) when something in it changes, and of course you can see the extent of the logic required to do that (just a few lines -- incidentally vastly simpler than was required in the old getSequencerSlice). But even assuming the intention is ultimately to rewrite only the part of the segment that has changed, I can't see that that's any harder: the logic is surely identical to that for writing the whole segment (you just write the fragment N times at intervals of the segment duration). And at least reading it is guaranteed to be simple. What are you anticipating would be complex? Chris ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
