On Sunday 12 Oct 2003 9:53 am, Guillaume Laurent wrote: > But it *is* comprehensible code right now. I just get the > ReferenceSegment, iterate on its events and construct MappedEvents > out of them just like I do with a normal segment.
The problem is that ReferenceSegment really is not a meaningful concept -- it's a historical accident. There's nothing to be gained by using Event to store time signature or tempo; it just means you need to know all about the particular properties they use, which should also not be exposed. And ReferenceSegment suggests something with a more general use (not the case) or that is related to a segment (not the case). I already regret storing TimeSignature in an Event at all, as it makes everyone assume they can turn up in Segments, which isn't true. Don't make the situation even worse, please. Far better IMHO to store the tempo map as a series of time/bpm (or rather bph, for precision) pairs, and the time signature map as a series of time/time-signature pairs. It's not like it's hard to get hold of those types -- they're exactly what the Composition's public API returns. Chris ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
