--- Tim Hockin wrote: > > Let's say you have a simple filter with one of it's parameters the > > filter type. > > In the first version of your plugin you have three possible filter > > types (low pass, band pass and high pass). Now, in a next version of > > your plugin you are now also supporting 3 extra filter types (notch, > > low shelving, high shelving). > > This control remains EXACT semantic compatibility with old data. Any > old data is valid. The range was widened. > > > >From what you wrote above, I understand that you consider a range > > change as a reason to make a new control with a different name. > > I wrote that as a response to one of the examples that was asked. > Someone (Marc?) asked about compatibility for a control whose range > changed, but I think he meant more generically 'semantics changed'. http://www-2.cs.cmu.edu/~tom7/csnotes/fall02/semantics.gif __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ---------------------------------------------------------------------- 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