On Mon, Apr 11, 2011 at 12:21:31AM +0200, Tim Goetze wrote:
I can very well see how a host author would want
plugin port
signatures to be stable, and I was never happy about invalidating this
assumption.
However, the evolved plugin doesn't even break ardour or its session
files, so the pragmatic thing is to just get on with it and not waste
as much breath on a triviality like this as we do now.
Shouldn't such situations be avoided by
1. Giving the new plugin version a new unique ID so it
can't be mistaken for the old one (and vice versa) and
2. Making sure that installing the new version does not
remove or hide the old one. Since the new version is not
a bugfix for the old one but actually something different
this seems to be the logical thing to do.
That way any existing sessions will just go on use the
version they knew. It's then up to the user to update
his/her session (or not).
Ciao,
--
FA