File: 08.depthfirst.pd

package info (click to toggle)
puredata 0.55.2%2Bds-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 20,508 kB
  • sloc: ansic: 118,824; tcl: 10,221; cpp: 9,327; makefile: 1,632; sh: 1,476; python: 152; xml: 98; awk: 13
file content (42 lines) | stat: -rw-r--r-- 1,342 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
#N canvas 528 56 468 574 12;
#X msg 70 63 1;
#X obj 141 123 + 1;
#X obj 284 212 print x1;
#X obj 212 154 print x2;
#X obj 284 122 + 1;
#X obj 284 154 + 1;
#X obj 284 183 + 1;
#X text 42 13 In Pd \, message passing is depth first \, so that in this patch:, f 46;
#X msg 115 310 1;
#X obj 154 340 + 1;
#X obj 115 339 f;
#X floatatom 115 371 5 0 0 0 - - - 0;
#X text 44 400 ... because the "depth" is infinite. The counters you've seen always have the message chain terminated somewhere in a cold inlet:, f 52;
#X msg 106 464 1;
#X obj 145 494 + 1;
#X obj 106 493 f;
#X floatatom 106 525 4 0 0 0 - - - 0;
#X obj 70 92 trigger float float float float;
#X obj 141 154 print x3;
#X obj 70 154 print x4;
#X text 44 247 ... you get "x1" first \, notwithstanding the fact that "x2" \, "x3" and "x4" appear to be closer to the source. This means that you shouldn't do this:, f 48;
#X text 106 63 <-- click here;
#X text 146 309 <-- maybe you shouldn't click here;
#X text 142 464 <-- better;
#X connect 0 0 17 0;
#X connect 1 0 18 0;
#X connect 4 0 5 0;
#X connect 5 0 6 0;
#X connect 6 0 2 0;
#X connect 8 0 10 0;
#X connect 9 0 10 0;
#X connect 10 0 11 0;
#X connect 10 0 9 0;
#X connect 13 0 15 0;
#X connect 14 0 15 1;
#X connect 15 0 16 0;
#X connect 15 0 14 0;
#X connect 17 0 19 0;
#X connect 17 1 1 0;
#X connect 17 2 3 0;
#X connect 17 3 4 0;