From 591854adb9ab77e04766c9ed01b28be9fd9b02a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Mon, 1 Sep 2008 14:36:04 +0000 Subject: renamed [parentposition] to [canvasposition] (consistent naming scheme); added more helppatches svn path=/trunk/externals/iem/iemguts/; revision=10272 --- help/sendcanvas-help.pd | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 help/sendcanvas-help.pd (limited to 'help/sendcanvas-help.pd') diff --git a/help/sendcanvas-help.pd b/help/sendcanvas-help.pd new file mode 100644 index 0000000..9f8b01d --- /dev/null +++ b/help/sendcanvas-help.pd @@ -0,0 +1,27 @@ +#N canvas 251 447 635 427 10; +#X obj 81 25 sendcanvas; +#X text 168 27 send messages to a (parent) canvas; +#X obj 88 151 sendcanvas; +#X msg 88 130 obj 300 150 f; +#X text 57 85 this object will send messages to a canvas \; by default +it will send a message to the canvas containing it:; +#X text 53 194 but you can also send to a message to a parent-canvas +(of any depth); +#N canvas 0 0 781 310 sendcanvas 0; +#X obj 147 72 inlet; +#X obj 147 166 sendcanvas 1; +#X msg 147 126 obj 300 250 print; +#X text 252 170 "1" means that the message is sent to the parent-patch +(depth:1); +#X connect 0 0 2 0; +#X connect 2 0 1 0; +#X restore 99 248 pd sendcanvas; +#X obj 99 229 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 +-1; +#X text 80 306 you can basically achieve this functionality with [namecanvas] +and an ordinary [send] \; so this object is merely convenient as you +can dynamify a canvas without prior thought to it; +#X text 58 295 note:; +#X text 72 390 (c) 2008 IOhannes m zmoelnig; +#X connect 3 0 2 0; +#X connect 7 0 6 0; -- cgit v1.2.1