I'm finally trying to write in C, and i wonder if there's a handy way to 

keep max opened while rebuilding the sources. Yet, i open max, use the 

"install" function (that seems to be temporary when your object is not 

in the search path, good to know), reload my test patch, close max, 

Even if any instance of my object is closed, it's always there in max 

memory, so i can't recompile it (file in use)...

f.e chanfrault | aka | personal computer music

> >>>>>> |sublime music for a desperate people|

I'm finally trying to write in C, and i wonder if there's a handy way to 
keep max opened while rebuilding the sources. Yet, i open max, use the 
"install" function (that seems to be temporary when your object is not 
in the search path, good to know), reload my test patch, close max, 
recompile, reopen max,...

Even if any instance of my object is closed, it's always there in max 
memory, so i can't recompile it (file in use)...

-- 
f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|


handy-way-for-external-update

> I'm finally trying to write in C, and i wonder if there's a handy 

> way to keep max opened while rebuilding the sources. Yet, i open 

> max, use the "install" function (that seems to be temporary when 

> your object is not in the search path, good to know), reload my 

> test patch, close max, recompile, reopen max,...

> Even if any instance of my object is closed, it's always there in 

> max memory, so i can't recompile it (file in use)...

Well known issue. Some people rename their objects as they make 

incremental changes (myobj1, myobj2, myobj3...) so they can install 

without restarting Max. Requires some editing of your test patch, but 

often faster than the launch/test/quit/build cycle.

Other people just live with it and exit/quit Max, rebuild, restart/ 

relaunch Max. There are worse development cycles. It also encourages 

you to think harder about what you're doing!-)

Peter Castine +--> Litter Power & Litter Bundle for Jitter

Interface Building for |home | chez nous|

Max/MSP Extremely cool |bei uns | i nostri|

> I'm finally trying to write in C, and i wonder if there's a handy  
> way to keep max opened while rebuilding the sources. Yet, i open  
> max, use the "install" function (that seems to be temporary when  
> your object is not in the search path, good to know), reload my  
> test patch, close max, recompile, reopen max,...
>
> Even if any instance of my object is closed, it's always there in  
> max memory, so i can't recompile it (file in use)...

Well known issue. Some people rename their objects as they make  
incremental changes (myobj1, myobj2, myobj3...) so they can install  
without restarting Max. Requires some editing of your test patch, but  
often faster than the launch/test/quit/build cycle.

Other people just live with it and exit/quit Max, rebuild, restart/ 
relaunch Max. There are worse development cycles. It also encourages  
you to think harder about what you're doing!-)

--------------    http://www.bek.no/~pcastine/Litter/    -------------
Peter Castine             +--> Litter Power & Litter Bundle for Jitter
                                Universal Binaries on the way
iCE:  Sequencing,  Recording &
       Interface  Building  for                   |home    | chez nous|
       Max/MSP   Extremely cool                   |bei uns |  i nostri|
       http://www.dspaudio.com/                   http://www.castine.de

Handy way for external update ?