[maxmsp] Re: Re: managing multiple patches

My workaround for this particular problem is module loading at patch  
runtime.

Any subpatches I need are kept in a module folder, which is specified  
in my patch as an argument to my module loading abstraction. When the  
patch is run it searches the modules folder and makes a full path to  
the subpatch. This removes any issues with file path issues or  
duplicate names, as the path is hard coded, etc.

it works, but makes loading a bit slower with larger amounts of modules.

just my 2.c workaround :)

On Feb 3, 2008, at 2:03 PM, Stefan Tiedje wrote:

> Mattijs Kneppers schrieb:
>> No, this is bad practice. If you have multiple versions of the same
>> abstraction hidden in the depths of the patches folder you will never
>> know which one is loaded. And yeah, the patches folder is advertised
>> in the manual. It shouldn't be.
>
> Though in most cases they have just my patch to run in MaxPlay. Its  
> less of a danger than in my own environment. And it wouldn't change  
> anything if they'd just add the folder to the search path, search  
> path is search path no matter if its in the patches folder or  
> elsewhere. And Murphy tought me, that its always the wrong version  
> loading if you have several of them no matter where you place  
> it... ;-)
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|\-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>
> _______________________________________________
> maxmsp mailing list
> maxmsp at cycling74.com
> http://www.cycling74.com/mailman/listinfo/maxmsp