On Tuesday 15 Aug 2006 08:34, Guillaume Laurent wrote: > I'm very tempted to enforce this at the composition level, > i.e. no composition can have less than 64 tracks.
I think that's a bad idea that wouldn't be at all popular with users. Remember that one of the trends of our current development is to increase the amount of meaningful data associated with each track. The track is becoming less like an arbitrary y coordinate for the segment, and more like an object that the user will want to tweak to their requirements. Consequently users will become more, rather than less, likely to want to make tidy compositions that have only the number of tracks they actually need. What's more, if we do ever get around to making a nice new-composition instrument selection wizard or dialog, we're likely to be creating compositions with far fewer than 64 tracks as a matter of routine. I think we should expect users to do that, and we need to cope with it properly. Chris ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
