[maxmsp] Re: Re: managing multiple patches
Mattijs Kneppers
mattijs at smadsteck.nl
Mon Feb 4 03:31:14 MST 2008
- Previous message: [maxmsp] Re: Re: managing multiple patches
- Next message: [maxmsp] Re: Re: managing multiple patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ok, I've been checking with a big patch that also does a fair amount of scripting on load and so far your solution seems to work great! Thanks again :) Btw by relying on synchronous events I think you could slightly simplify your patch: #P window setfont "Sans Serif" 9.; #P window linecount 1; #P newex 163 206 25 196617 iter; #P window linecount 2; #P message 163 174 347 196617 Sources/Images Sources/Librairie Sources/Preferences Sources/Presets Sources/Sons Sources/Sons/bank_1 Sources/Sons/bank_2; #P window linecount 1; #P newex 111 75 88 196617 t dispose b b path; #P newex 163 281 27 196617 t b l; #P newex 163 311 36 196617 zl reg; #P newex 163 422 51 196617 tosymbol; #P newex 163 395 72 196617 sprintf %s%s; #P newex 163 484 78 196617 prepend append; #P newex 163 521 98 196617 filepath search 100; #P newex 48 538 47 196617 pcontrol; #P newex 48 407 66 196617 prepend load; #P message 48 321 80 196617 real_patch.mxb; #P newex 175 452 153 196617 print "@ Patch :: paths loading"; #N thispatcher; #Q end; #P newobj 189 124 61 196617 thispatcher; #P newex 111 43 48 196617 loadbang; #P connect 9 0 7 0; #P connect 9 0 2 0; #P connect 12 2 13 0; #P connect 14 0 11 0; #P connect 13 0 14 0; #P connect 12 1 3 0; #P connect 12 3 1 0; #P connect 12 0 1 0; #P connect 0 0 12 0; #P connect 1 1 10 1; #P connect 11 1 8 1; #P fasten 7 0 6 0 168 518 168 518; #P connect 8 0 9 0; #P connect 10 0 8 0; #P connect 11 0 10 0; #P connect 4 0 5 0; #P connect 3 0 4 0; #P window clipboard copycount 15; Mattijs Quote: jln wrote on Sun, 03 February 2008 20:53 ---------------------------------------------------- > Quote: Mattijs wrote on Sun, 03 February 2008 18:45 > > > Yeah, I still have to try that idea. It doesn't feel good though, looking at the sometimes-synchronous-sometimes-not behaviour when creating larger abstractions with scripting.. > > I'm not sure I get what you mean here. To what extend the "sometimes-synchronous-sometimes-not" behaviour would cause problems using the strategy mentioned. When all the scripting part happens in the main patch, all paths are in Max's search preferences (until it is restarted), no ? > > I attach what I often use. I never had some troubles but never did a big patch involving a lot of scripting so maybe I'm missing something... > > Best, > Julien. ----------------------------------------------------
- Previous message: [maxmsp] Re: Re: managing multiple patches
- Next message: [maxmsp] Re: Re: managing multiple patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
