Jmax Phoenix does this. If I recall correctly it breaks the nested list
feature
in Gridflow.
But considering your [osc~ (pitch * 2)]
example-- what would happen if you change the value of pitch? The value
of the [osc~] object's argument is assigned to be the initial frequency only
when the object is created, so it doesn't seem like it would have an effect
unless you recreate the object. (I'm curious what Jmax Phoenix does in this
regard.)
-Jonathan
--- On Mon, 12/13/10, Andrew Faraday <jbtur...@hotmail.com> wrote:
From: Andrew Faraday <jbtur...@hotmail.com>
Subject: [PD] PD OOP?
To: pd-list@iem.at
Date: Monday, December 13, 2010, 10:34 PM
Hey All
I've had a bit of a daydream about a further development in PD. Could an
expression be placed into the arguments of an object, or even a named receive
become part of expr
I suppose the dream would be to have something like
[osc~ (pitch * 2)]
instead of
[r pitch]
|
[* 2]
|
[osc~]
or even
[expr pitch * 2]
|
[osc~]
And other such space-saving arguments.
Does anyone know of anything like this to streamline pd? Or am I just dreaming
here?
Cheers
Andrew
-----Inline Attachment Follows-----
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
