Right, I'm rofgetting, the "pd $0-x" ends up naming the canvas "pd-$0-x"
which is hard to generate as a symbol. My problem with "namecanvas" is that
one can free or rename the patch (or just free the namecanvas object itself in
the patch) and crash Pd. I still haven't found a clean alternative... so
for now, I'll have to keep the mis-designed "namecanvas" object around for
the forseeable future.
cheers
Miller
On Wed, Dec 29, 2004 at 10:42:05PM +0100, Tim Blechmann wrote:
hi miller, hi devs ...
i wrote an abstraction using message-based patching ...
therefor, i was sending the messages to pd-test.pd ...
but since it's an abstraction all other instances of test will receive
the same message, resulting in the multiple creation of the object ...
to solve this, i had to use namecanvas $0-test... and send the messages
there ... (example patch is attatched)
am i missing something obvious or is namecanvas not as obsolete as the
helpfile says...
cheers ... tim
After one look at this planet any visitor from outer space
would say "I want to see the manager."
William S. Burroughs
18 messages in at.iem.pd-dev[PD-dev] Re: is namecanvas obsolete o...
.pd, .pd, .pd