I agree too... Whenever something is available in Max and also in clashing libraries, I'm thinking of figuring out the Max compatible one (probably this will always be the one in cyclone) and putting that in the Pd core.
Also, objects such as abs~, etc., which are in cyclone but seem canonical should go into Pd. I haven't decided wheether Pd should try to include the whole of cyclone or not.
also, I want to add a flag to Pd to supperss loading specific classes so that, when classes are added to Pd , they don't break existing libraries quite so badly.
cheers Miller
On Tue, Jul 20, 2004 at 06:26:58PM +0200, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
I think that we should also use the cyclone [counter]. We should use the Max-compatible objects first, unless there is a very good reason to do otherwise. Other counter-type objects can just as easily have different names. Plus with many of the help files linking to all related objects, it makes it much easier to figure out which specific object serves your purpose.
I agree here. Max compatibility shouldn't be broken where not necessary.
Ciao
Frank Barknecht _ ______footils.org__
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list