> > 1) range change > > - make a new control** with the new range and a new name > > I personally don't like the idea that changing a parameter's range (or > another property) of a parameter would require you to make a new parameter > with a new name! That just doesn't feel right at all to me. It IS still the > same parameter, only some properties have changed, but it still has the same If a control is semantically compatible with an old version, then there is no reason to change it's name. If it is not compatible, well, then it really IS a different control, no? ---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission. Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe