hi Olaf,
there is more and more of that talk about name clashes...
In the maxlib, there are three clones of the native max classes: borax, match, and speedlim (scale is not native afaik). Two of them, match and speedlim, are in the cyclone too.
1. I would like to include Borax in cyclone at some point (but not yet). No name clash here, but how about me using your code when I come to that? I would need to adjust it to the cyclone's coding style, test for compatibility with max, etc.
2. The match in cyclone is based on Joseph Sarlo's code, rewritten to be able to match floats and symbols, handle any type of data, recognize overlapping patterns, etc. It is 'set'table (it is also growable, unlike the match of max), and supports generic 'nn' atoms.
3. The speedlim from maxlib lacks two important features of max original, and its cy-clone: it accepts only floats, and ignores input if blocked. The max4 reference manual:
*Input* anything In left inlet: The message is passed out the outlet, provided that a certain minimum time has elapsed since the previous output. Otherwise, the message is held until that amount of time has passed (or until it is overwritten by another incoming message).
Now, the question is: how many patches depend on match or speedlim from the maxlib? If not many, would you be willing to rename the two? Or do you see it the other way around?
Krzysz-the-sooner-the-better-either-way-of
Olaf Matthes wrote: ...
- match 0.3 now matches any type of data (floats, lists, symbols,
anything)
...
BTW, there's a scale object in maxlib that behaves like the on in Max... any suggestions because of the name clash with scale from Gem and others?