hi luke
On Thu, 2007-02-08 at 00:16 -0700, Luke Iannini (pd) wrote:
Thanks to both of yas! Should probably add this to puredata.org or something for posterity. Or a bug report since it's obviously a kludge.
a kludge? why?
anyway, why do you want to have a litteral '$0' in the abstraction argument and not the value, that it represents, since it is actually the same? if i am not totally mistaken, this would only make sense, when you plan to save the patch with all the dynamically generated stuff, whereas saving dynamically generated stuff does not make sense at all, as far as i can see it. the only case i could think of, that would require litteral '$0's as abstraction arguments, would be, if you would use dynamic patching just as a quicker way of patching.
roman
On 2/7/07, Chris McCormick chris@mccormick.cx wrote:
On Wed, Feb 07, 2007 at 07:54:40PM -0700, Luke Iannini (pd) wrote:
I'm trying to generate objects within a subpatch using [obj( messages, and I want those generated objects to have $0 as one of their arguments, e.g. [myobject $0]. Using [obj x y myobject $0( gives [myobject 0] (I know $0 is not for messages, just thought I'd give that a try), and of course [list append $0] to the object message just adds the interpreted $0 of the parent patch. I'd like to preserve the "$0". Anyone know of a way to do it?
Hi,
I think the attached patch demonstrates what you mean.
Best,
Chris.
chris@mccormick.cx http://mccormick.cx
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de