On Wed, Dec 23, 2015 at 4:44 AM, Dan Wilcox wrote:
> What about versioning? If people *have* to have older compatibility, then
> why can’t they just run an older version of cyclone? Newer development can
> take place on the current version and you can clearly note api
>
Oh I know. It just seems a shame to say: "Well, somebody might have a patch
somewhere from 10 years ago that relies on a 10 year old version of a library
that mimics a 10 year old version of Max running on a 10+ year old computer/os
and we can't break that, ever."
For vanilla objects yeah, I
> On Dec 23, 2015, at 9:08 AM, Dan Wilcox wrote:
>
> I’d make an abstraction wrapper around [count~] that filtered out the set
> message
Hah. never mind. I forgot PD chooses compiled objects over abstractions so you
can’t do what I suggested anyway. Teach me to type
>
> Hah. never mind. I forgot PD chooses compiled objects over abstractions so
> you can’t do what I suggested anyway. Teach me to type before following my
> own advice and “test it”.
>
you can still give warnings, if that's the case; but this seems like a
digression. Not sure if I get what katja
Hi --
1: Is the technique of setting object attributes via messages documented
anywhere?
(x2.html has most things, but I don't see this.)
2: Is there a list of all the standard objects, and the names of all
attributes (methods) which are settable via messages?
(A language specification or
On Wed, Dec 23, 2015 at 8:08 PM, William Huston
wrote:
> Hi --
>
> 1: Is the technique of setting object attributes via messages documented
> anywhere?
>
> Probably in the source code...
> ...
>
> 5: I would prefer to set an object's color via an RGB value
> Can I
On Tue, Dec 22, 2015 at 11:51 PM, 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.
Right, in