[maxmsp] Re: Re: Re: managing multiple patches
Mattijs Kneppers
mattijs at smadsteck.nl
Mon Feb 4 05:02:01 MST 2008
- Previous message: [maxmsp] Re: Re: managing multiple patches
- Next message: [maxmsp] Re: managing multiple patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Quote: jln wrote on Mon, 04 February 2008 12:35 ---------------------------------------------------- > 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. Actually I see a reason not to remove the 100. This way, it will not be a problem to open an older version of your patch first and then load a newer version without restarting max. If you remove the 100 there is a chance that the newer version will use files from the older version because the paths of the older version aren't overwritten. > > 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. Ah, I see. But that would also require a delay before loading the real patch. I don't get a graphics update until everything is loaded. Adding a slider in the launcher showing the progress of > the main patch initialization is also rather neat. :-) As far as I can see for this to work you'd need the graphics redraws to happen in a separate thread, which unfortunately isn't the case in max. Best, Mattijs
- Previous message: [maxmsp] Re: Re: managing multiple patches
- Next message: [maxmsp] Re: managing multiple patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
