julien breval

I am using a simple combination of "pattrstorage", "autopattr" and named objects for managing presets.

If I use priorities in "pattrstorage", as soon as I open the patch, Max/MSP considers that something has changed (in the patch itself, not among the pattr-saved parameters of the patch) and asks if I want to save the Max patcher before closing, even if I only open and immediately close it.

If no priority is set, I don't have this problem.

How can I have both priorities set to specific values AND Max never ask for saving the patcher ?

pattrstorage-priorities-and-patcher-saving

Am 22.03.2007 um 12:11 schrieb julienbreval:

> I am using a simple combination of "pattrstorage", "autopattr" and 

> If I use priorities in "pattrstorage", as soon as I open the patch, 

> Max/MSP considers that something has changed (in the patch itself, 

> not among the pattr-saved parameters of the patch) and asks if I 

> want to save the Max patcher before closing, even if I only open 

> If no priority is set, I don't have this problem.

> How can I have both priorities set to specific values AND Max never 

>
> Hello,
>
> I am using a simple combination of "pattrstorage", "autopattr" and  
> named objects for managing presets.
>
> If I use priorities in "pattrstorage", as soon as I open the patch,  
> Max/MSP considers that something has changed (in the patch itself,  
> not among the pattr-saved parameters of the patch) and asks if I  
> want to save the Max patcher before closing, even if I only open  
> and immediately close it.
>
> If no priority is set, I don't have this problem.
>
> How can I have both priorities set to specific values AND Max never  
> ask for saving the patcher ?
>
>
> Thanks for your help
> -j
>


Thanks a lot Jeremy, I had missed that @dirty attribute

pattrstorage priorities and patcher saving