hi list do i unterstand it right, that subpatches are only for make patches "cleaner", and no way to commit some arguments individually , like we can do with abstractions? this would make a lot of things easyer, for example: copy paste a subpatch ,give them some arguments, and then i can change some little things in the individual subpatches...
i ask me then, why we can stop the audio with [switch~] in subpatches, or handle "canvas"-locality with [sendlocal] from guenter geiger
do i have overlook something? is there a "hack" to become the subpatchname?
thanks, and i hope this is not asked to much before.. moritz
Hey,
I think here the idea is that if you are going to use the same bit of patch in multiple "parent" patches then what you want IS an abstraction not a subpatch. Why would we make the subpatch like an abstraction when we have abstractions?
I think args to subpatches are ignored.
b?
moritz w. wrote:
hi list do i unterstand it right, that subpatches are only for make patches "cleaner", and no way to commit some arguments individually , like we can do with abstractions? this would make a lot of things easyer, for example: copy paste a subpatch ,give them some arguments, and then i can change some little things in the individual subpatches...
i ask me then, why we can stop the audio with [switch~] in subpatches, or handle "canvas"-locality with [sendlocal] from guenter geiger
do i have overlook something? is there a "hack" to become the subpatchname?
thanks, and i hope this is not asked to much before.. moritz
On Mon, Jun 06, 2005 at 04:38:57PM +0200, moritz w. wrote:
hi list do i unterstand it right, that subpatches are only for make patches "cleaner", and no way to commit some arguments individually , like we can do with abstractions? this would make a lot of things easyer, for example: copy paste a subpatch ,give them some arguments, and then i can change some little things in the individual subpatches...
subpatches share the 'locality' of the containing patcher, as far as $0 goes, but it soudns like youre looking for the ability to 'subclass' an abstraction and just change a few things? or perhaps real local-variables or symbols without makefilename+$0 hacks, or even the ability to pass distinct args to a subpatch like you can with an abstraction? keep waiting, or add it yourself..i think some work on these things, along with lists-within-lists and threads, pd could become the 'python or ruby' of dataflow langages..but it hasnt happened yet.
i ask me then, why we can stop the audio with [switch~] in subpatches, or handle "canvas"-locality with [sendlocal] from guenter geiger
do i have overlook something? is there a "hack" to become the subpatchname?
thanks, and i hope this is not asked to much before.. moritz
-- Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie! Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, ix@replic.net hat gesagt: // ix@replic.net wrote:
subpatches share the 'locality' of the containing patcher, as far as $0 goes,
Also as far as $1, $2 etc. go: subpatches take $1 from the surrounding abstraction. Because of that, subpatch arguments, if they should be implemented at all, must use different symbols, like #1, #2 etc. to keep older patches from breaking.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "scans" _ http://footils.org/cms/show/41
-
B. Bogart -
Frank Barknecht -
ix＠replic.net -
moritz w.