Forums > MaxMSP

pattr – See object but don't store (alternative to Active)

May 13, 2007 | 8:33 pm

Hi,

I want an object visible to the pattr hierarchy for control purposes but not stored in pattrstorage.

I know can use the "Active" command with pattrstorage.

Is there a technique/workaround for making the non-storage property local to the object?

The object is part of a subpatch that I reuse. Instead of having to send the "Active" command every time I reuse the subpatch in a different application, I’m looking for a technique local to the actual subpatch and object.

I’ve played around with pattr, autopattr, etc., in the subpatch but can’t find a logic that works.

Thanks for any help.

Adam


May 14, 2007 | 2:18 pm

Adam Kendall schrieb:
> Is there a technique/workaround for making the non-storage property
> local to the object?

pattrstorage attribute: @greedy 2

If you want visibility of single objects inside subpatchers, place a
pattr and bind it to that object…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


May 15, 2007 | 10:07 am

still, an @store attribute (default 1) to pattr wouldn’t be a bad idea at all.

Mattijs


May 17, 2007 | 12:11 am

Thanks, Stefan.

If I understand this solution correctly, I will have to actively include every control except the ones I want to exclude, right?

If so, it will cause too much work. I only have a couple of controls I want to exclude, but dozens that need to be included.

I’ll experiment with it.

Thanks.

Adam


May 18, 2007 | 3:52 pm

Adam Kendall schrieb:
> If I understand this solution correctly, I will have to actively
> include every control except the ones I want to exclude, right?
>
> If so, it will cause too much work. I only have a couple of controls
> I want to exclude, but dozens that need to be included.

What about autopattr? there is an exclude outlet…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


May 19, 2007 | 12:06 am

Unless I’m mistaken, that also excludes the object from the hierarchy. My goal is having objects that are recognized by the hierarchy for control purposes but not saved in pattrstorage.

Thanks.

Adam


May 22, 2007 | 10:28 am

You can talk to any named object, regardless of its visibility to
pattrstorage. Even via pattrstorage
("patcher::subpatcher::my_excluded_object 275"), or use pattrforward.

jb

Am 19.05.2007 um 02:06 schrieb Adam Kendall:

>
> Unless I’m mistaken, that also excludes the object from the
> hierarchy. My goal is having objects that are recognized by the
> hierarchy for control purposes but not saved in pattrstorage.
>
> Thanks.
>
> Adam


May 23, 2007 | 4:12 pm

Adam Kendall schrieb:
> Unless I’m mistaken, that also excludes the object from the
> hierarchy. My goal is having objects that are recognized by the
> hierarchy for control purposes but not saved in pattrstorage.

Did you try?

The proof should have been your part:

#P window setfont "Sans Serif" 9.;
#P number 331 178 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 1;
#P newex 331 203 99 196617 pattrforward rosie;
#P number 166 285 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P objectname minnie;
#P number 118 285 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P objectname rosie;
#P newex 81 179 81 196617 autopattr;
#X prestore minnie 1 0 0;
#P objectname u422000002;
#P newex 230 91 115 196617 pattrstorage huba;
#X client_rect 20 74 660 314;
#X storage_rect 0 0 640 240;
#P objectname huba;
#P connect 5 0 4 0;
#P connect 1 1 2 0;
#P window clipboard copycount 6;


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


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