i guess it would help for debugging of newer patches on older versions of
pd.
if you create [send x] and feed it [symbol x] [symbol y] symbol z], then it
will always send to x in older versions of pd, so it might be harder to find
the source of error. however, if you just create [send], it will
Hallo,
IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
> that is: if your create a [send] object without(!) a send-name, it will
> have a second inlet which can be used to set the send-name.
Which reminds me: Why was it made so that only sends without argument
get the second inlet?
ah good. thanks for clearing that up.
___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
hard off wrote:
> to follow on from a previous thread,
>
> how does the settable send work in pd 0.40 (i haven't installed it yet)
>
> if it is just like:
>
> [set x(
> |
> [send y]
>
> then, won't this break backwards compatibility? i often use [send] to
> pass set messages on, particularly
to follow on from a previous thread,
how does the settable send work in pd 0.40 (i haven't installed it yet)
if it is just like:
[set x(
|
[send y]
then, won't this break backwards compatibility? i often use [send] to pass
set messages on, particularly for example when using [tabread4~]
__
