On Wednesday, May 26, 2010, Yves Guillemot wrote: > -2) Because a complex segment requiring several time signatures would be > very different from the current short triggered segment. To call such a > long segment through the elsewhere discussed "segment link" should > probably be better than to call it through some triggering note or > ornament symbol.
Well, now that the question of time signature has been brought up, it seems pretty clear to me there is no really good way to handle the "segment symlink" concept at all in a scenario where different time signatures are involved. I'm not sure if this is best treated as one of those things where users have the power to do something stupid, and the responsibility to avoid it, or if we should just cease and desist on the whole idea on these grounds. Time is and always will be global, and there can never be any concept of embedding time in a discrete, modular, portable component. Rosegarden has global time and global tempo purely for our own sanity, and I can't see this ever changing. > -The current triggered segment mechanism seems an interesting prototype for > what may be some day a linked segment with transformations. My thought generally on triggered segments is they're best left pretty much alone in their current state, and any linked segment mechanism might borrow code and ideas, but it should not confuse itself or its purpose by thinking of itself as a "triggered segment" in any way. -- D. Michael McIntyre ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
