Revised and added to all_about help patches

svn path=/trunk/; revision=13941

1 files changed, 68 insertions, 53 deletions

diff --git a/doc/pddp/all_about_scope_and_locality.pd b/doc/pddp/all_about_scope_and_locality.pd
index 03e93858..9d482551 100644
--- a/doc/pddp/all_about_scope_and_locality.pd
+++ b/doc/pddp/all_about_scope_and_locality.pd
@@ -1,48 +1,51 @@
-#N canvas 166 111 516 471 10;
-#X text 9 34 WHAT IS THIS ALL ABOUT?;
-#X text 21 60 Depending on the complexity of your patches \, you may
+#N canvas 0 0 448 395 10;
+#X obj 1 1 cnv 15 445 20 empty \$0-pddp.cnv.header scope_and_locality
+20 10 1 18 -261106 -33289 0;
+#X obj 407 2 pddp/pddplink http://puredata.info/dev/pddp -text pddp
+;
+#X text 20 36 Depending on the complexity of your patches \, you may
 need to control whether or not messages will be used by only ONE patch
 \, or throughout all open patches. The scope of a message is considered
 either 'local' or 'global'.;
-#N canvas 146 223 606 389 GLOBAL_SCOPE 0;
-#N canvas 0 22 254 169 example_a 0;
-#X obj 18 9 r foo;
-#X floatatom 18 34 5 0 0 0 - - -;
-#X obj 24 96 r a-foo;
-#X floatatom 24 116 5 0 0 0 - - -;
+#N canvas 16 214 428 369 Global_scope 0;
+#N canvas 1 1 254 169 example_a 0;
+#X obj 18 19 r foo;
+#X floatatom 18 44 5 0 0 0 - - -;
+#X obj 18 96 r a-foo;
+#X floatatom 18 116 5 0 0 0 - - -;
 #X connect 0 0 1 0;
 #X connect 2 0 3 0;
-#X restore 34 56 pd example_a;
-#N canvas 2 238 256 163 example_b 0;
-#X obj 12 9 r foo;
-#X floatatom 12 28 5 0 0 0 - - -;
-#X obj 15 74 r b-foo;
-#X floatatom 15 93 5 0 0 0 - - -;
+#X restore 14 56 pd example_a;
+#N canvas 121 2 256 168 example_b 0;
+#X obj 18 19 r foo;
+#X floatatom 18 44 5 0 0 0 - - -;
+#X obj 18 96 r a-foo;
+#X floatatom 18 116 5 0 0 0 - - -;
 #X connect 0 0 1 0;
 #X connect 2 0 3 0;
-#X restore 155 57 pd example_b;
-#N canvas 0 473 231 169 example_c 0;
-#X obj 12 8 r foo;
-#X floatatom 12 30 5 0 0 0 - - -;
-#X obj 12 65 r c-foo;
-#X floatatom 12 86 5 0 0 0 - - -;
+#X restore 14 81 pd example_b;
+#N canvas 215 2 263 169 example_c 0;
+#X obj 18 19 r foo;
+#X floatatom 18 44 5 0 0 0 - - -;
+#X obj 18 96 r a-foo;
+#X floatatom 18 116 5 0 0 0 - - -;
 #X connect 0 0 1 0;
 #X connect 2 0 3 0;
-#X restore 269 57 pd example_c;
-#X text 377 58 Open these subpatches.;
-#X obj 43 142 s foo;
-#X floatatom 43 126 5 0 0 0 - - -;
-#X text 33 85 Click-n-drag these number boxes and notice the appropriate
+#X restore 14 106 pd example_c;
+#X text 17 38 Open these subpatches.;
+#X obj 23 187 s foo;
+#X floatatom 23 166 5 0 0 0 - - -;
+#X text 13 125 Click-n-drag these number boxes and notice the appropriate
 receive objects in each open sub-patch.;
-#X floatatom 102 126 5 0 0 0 - - -;
-#X floatatom 179 126 5 0 0 0 - - -;
-#X floatatom 252 126 5 0 0 0 - - -;
-#X obj 102 142 s a-foo;
-#X obj 179 142 s b-foo;
-#X obj 252 142 s c-foo;
+#X floatatom 82 166 5 0 0 0 - - -;
+#X floatatom 159 166 5 0 0 0 - - -;
+#X floatatom 232 166 5 0 0 0 - - -;
+#X obj 82 187 s a-foo;
+#X obj 159 187 s b-foo;
+#X obj 232 187 s c-foo;
 #X text 18 23 GLOBAL SCOPE - send and receive messages in ALL OPEN
 PATCHES;
-#X text 35 177 Send objects simply post their information to the cyberspace
+#X text 15 217 Send objects simply post their information to the cyberspace
 within your computer (that's one way to look at it!) Receive objects
 simply keep their ears open for all messages floating through that
 cyberspace from send objects of the same name! Hence \, if you name
@@ -51,12 +54,15 @@ patches named "foo" will 'hear' those messages. Also note that the
 term 'open patches' includes all sub-patches \, abstractions and patches
 that are currently open in Pd - they don't have to be VISIBLE...they
 only have to be active.;
+#X obj 1 1 cnv 15 425 20 empty \$0-pddp.cnv.subheading empty 20 10
+1 18 -261106 -33289 0;
+#X text 7 1 Global Scope;
 #X connect 5 0 4 0;
 #X connect 7 0 10 0;
 #X connect 8 0 11 0;
 #X connect 9 0 12 0;
-#X restore 11 157 pd GLOBAL_SCOPE;
-#N canvas 146 22 618 662 LOCAL_SCOPE 0;
+#X restore 23 94 pd Global_scope;
+#N canvas 146 22 618 662 Local_scope 0;
 #X text 4 9 LOCAL SCOPE -send and receive messages within a SINGLE
 PATCH;
 #X text 13 37 There are many cases where you may want messages to be
@@ -82,7 +88,7 @@ I used when I created the abstraction called "all_about_scope_and_locality".
 These two agruments are now available in this patch by using \$1 or
 \$2 variables. There's more information about this in the section called
 'Inheritance'.;
-#X text 13 267 In the examples above I have used a variable ($1) to
+#X text 13 267 In the examples above I have used a variable (\$1) to
 name these [send] and [receive] objects. The value of this variable
 is assigned either by Pd (randomly for each abstraction or patch) \,
 or by me with the use of arguments.;
@@ -105,8 +111,8 @@ you should see:;
 #X connect 8 0 7 0;
 #X connect 10 0 14 0;
 #X connect 13 0 11 0;
-#X restore 11 186 pd LOCAL_SCOPE;
-#N canvas 145 31 610 615 INHERITANCE 0;
+#X restore 23 119 pd Local_scope;
+#N canvas 145 31 610 615 Inheritance 0;
 #X text 20 18 The word "Inherit" means to "receive a characteristic
 from one's parent".;
 #X text 19 59 In Pd \, all abstracions and subpatches have 'parents'
@@ -126,7 +132,7 @@ this abstraction and all of its subpatches!;
 8 -262144 -1 -1;
 #X symbolatom 146 356 0 0 0 0 - - -;
 #X obj 146 327 symbol \$2;
-#X text 24 388 So \, if a [send] object is named "$1-foo" or "$2-foo"
+#X text 24 388 So \, if a [send] object is named "\$1-foo" or "\$2-foo"
 inside this abstraction \, Pd identifies that [send] object as "and-foo"
 or "inheritance-foo".;
 #X obj 47 466 s and-foo;
@@ -157,17 +163,26 @@ or "inheritance-foo".;
 #X connect 15 0 18 0;
 #X connect 16 0 20 0;
 #X connect 19 0 17 0;
-#X restore 11 217 pd INHERITANCE;
-#X text 16 285 From section 2.6.5 of the Pd manual \, Miller Puckette
-says:;
-#X text 39 316 "Note that the expansion of variables such as \$0 and
-\$1 only works at the beginning of the symbol. So \, for instance \,
-[rats-$1] will not be expanded. Occasionally you may want to have double
-or triple sustitutions. This can be done one stage at a time by nesting
-abstractions (with each subpatch adding its own $-variable to the begining
-of a symbol and passing that on as agrument to a further abstraction."
-;
-#X text 7 261 MILLER'S WISDOM;
-#X obj 4 4 cnv 15 500 20 empty empty all_about_scope_and_locality 20
-10 1 18 -233017 -66577 0;
-#X obj 471 5 pddp/pddplink http://puredata.info/dev/pddp -text pddp;
+#X restore 23 144 pd Inheritance;
+#X text 115 119 <- confusing \, clean it up;
+#X obj 1 373 cnv 15 445 20 empty \$0-pddp.cnv.footer empty 20 12 0
+14 -233017 -33289 0;
+#N canvas 44 246 494 344 META 0;
+#X text 12 85 HELP_PATCH_AUTHORS Dave Sabine \, May 5 \, 2003 . Jonathan
+Wilkes revised the patch to conform to the PDDP template for Pd version
+0.42.;
+#X text 12 65 LIBRARY PDDP;
+#X text 12 5 GENRE all_about_pd;
+#X text 12 25 KEYWORDS nonlocal needs_work;
+#X text 12 45 DESCRIPTION notions of scope in Pd;
+#X restore 392 375 pd META;
+#N canvas 11 243 428 121 Related_objects 0;
+#X obj 1 1 cnv 15 425 20 empty \$0-pddp.cnv.subheading empty 3 12 0
+14 -261106 -33289 0;
+#X text 7 2 Scope and Locality- Related Objects;
+#X restore 103 375 pd Related_objects;
+#X obj 6 375 pddp/pddplink pddp/help.pd -text help;
+#X obj 59 349 pddp/pddplink ../2.control.examples/14.dollarsigns.pd
+-text doc/2.control.examples/14.dollarsigns.pd;
+#X obj 59 334 pddp/pddplink all_about_dollarsign_zero.pd;
+#X text 52 209 This help file is unfinished.;