Forums > Dev

Objects owning patchers

Feb 08 2009 | 10:00 pm


I’m trying to port an object of mine to Max 5 that can load multiple patches inside itself.

I’ve managed to replace most of the stuff I was using before in order to deal with the patchers, but I’m stuck on a few final things that I can’t find covered in the api.


Before I was associating the patchers and subpatchers where necessary by setting the p->p_assoc field of the patcher struct.

I was also able to set the p_noedit field so that the patcher couldn’t be edited.

I was doing this so that closing the patcher window didn’t free the patcher when you closed it:

((t_wind *)PatchSpPtr->thepatch->p_wind)->w_refcount = 1;

I was doing this on the callback to say the window had been closed:

wind_invis((t_wind *)x->PatchSpPtr[index]->thepatch->p_wind);

I can’t figure out how to do any of these things under Max 5. Anyone any ideas on what I should be doing for any/all of these?

Many Thanks,


Viewing 1 post (of 1 total)

Forums > Dev