aboutsummaryrefslogtreecommitdiff
path: root/doc/tutorials/intro/ordering_messages.pd
blob: b7d454dbb6aa12e49c30c852a8c255ff88f50a83 (plain)
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 542 117 623 439 12;
#X obj -60 8 cnv 15 400 40 empty empty ordering_messages 20 12 0 24
-228992 -66577 0;
#X msg 395 249 now;
#X msg 316 250 this;
#X msg 237 250 makes;
#X msg 158 250 sense;
#X msg 80 250 !;
#X msg 276 391 sense now this;
#X obj 157 292 symbol;
#X msg 159 151 bang;
#X msg -27 177 bang;
#X msg 157 316 add2 \$1;
#X msg 478 248 set;
#X obj 160 178 trigger bang bang bang bang bang bang;
#X text -18 393 look here for the result -->;
#X text -50 62 Officially \, the execution order in Pd is undefined.
;
#X text -50 88 The [trigger] object allows you to specify the order
of messages are sent. If you need to make sure that one thing runs
before another \, use [trigger]:;
#X connect 1 0 7 0;
#X connect 2 0 7 0;
#X connect 3 0 7 0;
#X connect 4 0 7 0;
#X connect 5 0 7 0;
#X connect 7 0 10 0;
#X connect 8 0 12 0;
#X connect 9 0 3 0;
#X connect 9 0 5 0;
#X connect 9 0 11 0;
#X connect 9 0 4 0;
#X connect 9 0 1 0;
#X connect 9 0 2 0;
#X connect 10 0 6 0;
#X connect 11 0 6 0;
#X connect 12 0 5 0;
#X connect 12 1 4 0;
#X connect 12 2 3 0;
#X connect 12 3 2 0;
#X connect 12 4 1 0;
#X connect 12 5 11 0;