If I may make a suggestion - when I find that an object isn't terribly well designed (for example my own qlist :) I make another one, with another name, that does the job better (text).
cheers Miller
On Tue, Dec 22, 2015 at 08:51:03PM -0200, Alexandre Torres Porres wrote:
Well, newer patches with newer functionalities not working in older versions is how things go anyway, right? Vanilla 0-46 patches don't run in 0.45 and so on... there's no way around that I guess.
the dual outlet layout with message left and signal right is rather unusual.
But I think it's also simpler and more straightforward than introducing flags, arguments and all. It might be unusual, but there are already some objects with similar design, I actually thought of that because of [sampstoms~] and [mstosamps~] - it'd be basically the same design.
cheers
2015-12-22 19:48 GMT-02:00 katja katjavetter@gmail.com:
On Tue, Dec 22, 2015 at 9:41 PM, Alexandre Torres Porres porres@gmail.com wrote:
If we're discussing [average~], how about my idea of having a second
right
signal outlet as default? I think it's an easy and simple solution. Help file would explain how the left control outlet is for backwards compatibility. Done.
Yes that would be an easy way to incorporate Fred Jan's signal average output into the existing class. But note that both solutions, dual mode and dual outlet, have a similar forward incompatibility effect. A patch that uses the right signal outlet of a new version won't run with an old average~ binary. So the pros and cons of both solutions are comparable, with the small difference that the dual outlet layout with message left and signal right is rather unusual.
Katja
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list