Forums > MaxMSP

pattrstorage – priorities issue

Nov 08 2010 | 2:45 pm


Isn’t it possible to set priorities of some items that are within abstractions, from the top level patcher?
I’m probably missing something here…

Here is an example patch showing what I would like to achieve :

-- Pasted Max Patch, click to expand. --

(this example uses embedded bpatchers instead of abstractions, but that’s the same issue)



Nov 08 2010 | 8:11 pm

You are just missing a colon. You want something like, ‘priority A::A_number $1’ and ‘priority A::B::B_number $1’.

One thing, setting the priority of ‘A’ or ‘B,’ which are patchers, doesn’t really make any sense, at least to me.


Nov 08 2010 | 8:51 pm

…ok! :)
Thanks for pointing out my typo mistake.

Patchers’ priorities make sense to me. I think that if A got a lower priorities than B, its items will be restored first, even if all the items in A and B got the same priorities. At least I expect it. gonna give it a try.


Nov 08 2010 | 10:45 pm

One can set the topmost patcher’s priority, but subsequent patchers within the hierarchy will always be restored top down. From the ref:

"Priority is only respected within a single level of the patcher hierarchy. Data in parent patchers will always be restored before data in nested patchers."


Nov 08 2010 | 11:32 pm

Yes, sorry, the A and B of my example patch were not a good example for that.
In my last post I was thinking of A and B as two patches at the same level.

Viewing 5 posts - 1 through 5 (of 5 total)

Forums > MaxMSP