[maxmsp] Re: Re: How to apply oo within Max

Quote: adamj wrote on Thu, 01 November 2007 05:56
----------------------------------------------------
> Quote: Mattijs wrote on Wed, 31 October 2007 09:41
> ----------------------------------------------------
> > - when encapsulating something you have to change all the pattr paths that connect to and from the newly created subpatch. pattr doesn't allow for unnamed intermediate subpatchers. The pattr namespace is still global so not usable in a situation where scope is important.
> 
> The namespace issue is definitely a headache. It makes it tough to rework the structure of a large patcher hierarchy once the pattr system has been introduced. I don't think it's an issue with the global namespace or scope, though. In the attached patch you can message pattrs using a relative path from any point in the patch. Abstractions can be reused no problem. Or use the fully qualified path from the top level. How is it not usable where scope is important? 
>

Ah no, I was talking about the pattrmarker object, the equivalent of a namespace in C++. pattrmarker could be used to connect to pattrs without having to specify every intermediate patcher in the path, but pattrmarker defines a global name, so is not usable when you need an independent scope.

Mattijs
--
SmadSteck - http://www.smadsteck.nl
Hard- and software for interactive audiovisual sampling