hi miller, hi list !
using pd with the ("experimental") scalar object is painful, especially if you (like me) are trying to use it in abstractions that are used more than one time.
the problems are:
default. thus you cannot use "namecanvas my_template" within the sub, since the "set"(...) routines will fail. the "scalar"-object itself does *not* add the leading "pd-". so you have to create objects: "scalar pd-my_template float X" and "get my_template X" to address the same template. i do not think that this is consistent. it is not possible to use multiple namespaces within a subpatch (with "namecanvas"), which is ok, but does not help to work around the inconsistency.
"pd-my_template" will be created. however, this does not work with $args, so "pd $0_template" will create a namespace like "pd-$0_template" instead of (for instance) "pd-1001_template"
i considered these as bugs and tried to fix them:: so now the behaviour is as follows:
the other traversal objects 2) the $args are correctly expanded for the namespace of a subpatch
i fixed the help-files (5.reference/scalar.pd and 7.stuff/data-structures/8.panel.pd) accordingly.
the patch does not fix the instability of the traversal/scalar-objects !! (so it will keep crashing when used ;-)
since i am going to use this heavily now, i hope that i could make it into the next release (or something similar, that let's me use multiple abstractions with templates and drawings on the parent-patch)
mfg.csd.asdf IOhannes
the patch is attached and (or alternatively the source-code) can be found on ftp://iem.kug.ac.at/pd/misc/
mfg.cds.sdaf IOhannes