Oops! I'm using "dsp" for objects to intercommunicate, but I had meant to protect anyone from stumbling on it. Obviously I missed something.
I can suggest many possible workarounds, but will get around to fixing this someday.
cheers Miller
On Tue, Apr 01, 2008 at 06:05:37PM +0200, matteo sisti sette wrote:
Hi,
This must have been discussed in the list before, but I couldn't find anything in the archives because it's difficult to generate a meaningful set of keywords for this......
In a merely fortuitous way, I found out that if you send a message starting with the keyword "dsp" into an inlet of a subpatch or abstraction, it is not passed through the inlet.
Attached is an example, i.e.:
[ ( | [pd mysubpatch]
where the subpatch contains:
[inlet] | [print]
If you write "dsp something" in the message and click it, the message won't be printed!!!! (while any other message will)
It seems like the inlet itself "catches" it...
I don't know what [inlet] is supposed to do with messages starting with "dsp". I thought it may perhaps switch~ off the subpatch, but it doesn't.
Is this a bug or a feature? Is it documented somewhere?
Thanks m.
-- Matteo Sisti Sette matteosistisette@gmail.com http://www.matteosistisette.com
#N canvas 667 288 450 300 12; #N canvas 689 62 450 300 mysubpatch 0; #X obj 169 51 inlet; #X obj 169 96 print DATA; #X connect 0 0 1 0; #X restore 147 184 pd mysubpatch; #X msg 80 124 1 2 3; #X msg 120 92 bla bla bla; #X msg 153 148 dsp 1; #X connect 1 0 0 0; #X connect 2 0 0 0; #X connect 3 0 0 0;
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list