#N canvas 285 247 548 293 10; #X obj 4 4 cnv 15 400 40 empty empty empty 20 12 0 14 -262130 -66577 0; #X text 29 253 docs based on the MAX/MSP reference (c) cycling'74; #X text 28 267 ___________________________________________________ ; #X obj 35 28 past; #X text 81 27 report when input increases beyond a certain number; #X obj 59 165 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 59 138 past 4; #X floatatom 59 63 5 0 0 0 - - -; #X text 112 140 one arg sets the limit to get past; #X msg 102 104 set 8; #X text 145 104 (re)set the limit to pass by; #X msg 102 77 clear; #X text 142 78 forget previous input; #N canvas 133 162 577 369 weirdness 0; #X obj 97 178 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X floatatom 27 55 5 0 0 0 - - -; #X msg 138 55 set 10 20 30; #X obj 27 103 pack f f; #X obj 27 79 t f f; #X obj 97 147 past 2 5; #X msg 177 98 20 30 40; #X msg 177 78 0 0 0; #X msg 177 118 40 20 wrdlbrnft; #X msg 375 72 11 22 33; #X obj 375 176 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 375 150 past 10 20 30; #X msg 346 48 0 0 0; #X msg 397 93 11 33; #X msg 411 113 33; #X text 94 19 now theses are a bit strange IMO:; #X text 50 259 this is a quote from an email Krzysztof Czaja sent me: ; #X text 49 276 > it's list handling is weird indeed \, it bangs if _any_ list; #X text 49 288 > item is greater than (>) a corresponding threshold \, or if; #X text 50 300 > _all_ list elements are greater or equal (>=). That is how; #X text 50 312 > it looks like in Max but I might be wrong ...; #X connect 1 0 4 0; #X connect 2 0 5 0; #X connect 3 0 5 0; #X connect 4 0 3 0; #X connect 4 1 3 1; #X connect 5 0 0 0; #X connect 6 0 5 0; #X connect 7 0 5 0; #X connect 8 0 5 0; #X connect 9 0 11 0; #X connect 11 0 10 0; #X connect 12 0 11 0; #X connect 13 0 11 0; #X connect 14 0 11 0; #X restore 349 187 pd weirdness; #X text 33 192 I don't fully understand the list behaviour:; #X connect 6 0 5 0; #X connect 7 0 6 0; #X connect 9 0 6 0; #X connect 11 0 6 0;