Chris Muir

Is there a way to exclude bpatchers from being exposed to a top-level 

autopattr, other than connecting the bpatcher to the top level 

I thought I could just not give the bpatcher a scripting name, but one 

is generated automatically if the bpatcher contains its own autopattr.

Is there a way to exclude bpatchers from being exposed to a top-level  
autopattr, other than connecting the bpatcher to the top level  
autopattrs exclude outlet?

I thought I could just not give the bpatcher a scripting name, but one  
is generated automatically if the bpatcher contains its own autopattr.

exclude-from-autopattr

Does't/can't the active message apply to
all the "children" of a parent node,
too? Perhaps I'm misunderstanding the
question....


Chris, did you ever figure this out? I'm dealing with the same issue right now.

exclude from autopattr