[maxmsp] Re: Re: managing multiple patches
Rabin Julien
julien.rabin at gmail.com
Mon Feb 4 04:35:47 MST 2008
- Previous message: [maxmsp] Re: Re: managing multiple patches
- Next message: [maxmsp] Re: Re: Re: managing multiple patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le 4 févr. 08 à 11:31, Mattijs Kneppers a écrit : > 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 Thanks. I'm glad I can help. You're right. I often use this template from an old project but indeed, I should have optimized it since. Looking at it again, the '100' argument should be removed from [filepath] so paths are not saved in Max's preferences on quit. It's not a big problem but I guess people don't want their preferences to be changed by my patch. The reason I send the 'dispose' message from the main patch is only cosmetic. As I use the launcher patch as a pseudo appsplash, I like seeing it going away only when the main patch is ready and fully initialized. Adding a slider in the launcher showing the progress of the main patch initialization is also rather neat. :-) Best, Julien.
- Previous message: [maxmsp] Re: Re: managing multiple patches
- Next message: [maxmsp] Re: Re: Re: managing multiple patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
