Forums > MaxMSP

Duplicated structures without interferences using "—-" ?


Dec 06 2010 | 3:56 pm

Hello,

#0 is a way to give specific names to objets within a subpatch to avoid interferences between multiple instances. However as it implies random numbers, I remember that a long time ago it was possible to use "—-" as a prefix to achieve the same results.

It doesn’t seem to work anymore. Or am I using it the wrong way?


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

Dec 06 2010 | 5:53 pm

"—" only worked in the pluggo context (it now works in Max for Live). If you want to have independent bpatchers, you can use #0, if you want them all to communicate, pass an argument to the bpatchers, and grab it with #1.

Dec 07 2010 | 4:52 pm

Ok thanks !


pid
Dec 07 2010 | 6:20 pm

hi emanuel. i knew all this. but when vizzie was released i noticed that it too uses "—". seeing as vizzie is just a collection of bpatchers, how is it using the "—"? i asked this in another thread but no-one picked up. i’d be interested if there was a way to utilise it in a vizzie-like context. could you clarify?

thanks.

Dec 08 2010 | 4:36 pm

The original idea was that this would be a polite thing to do for Max for Live users. The unintended consequence of this would-be act of charity was that it implied to Max users that — worked in Max proper, which (as my colleague Emmanuel has pointed out) isn’t so. In any case, it works fine – it merely confuses people who actually write and look at Max patches, which would seem to argue for its elimination. :-)


pid
Dec 08 2010 | 4:52 pm

thanks gregory. funny, i really enjoy reading your replies when they are directed at someone else, but directed at me and i just think, well, that was completely useless and cryptic. so, anyone else wanna reply? preferably in english equipped for a 2 year old to understand?

Dec 08 2010 | 6:32 pm

in frenglish, it sounds like this… The used in vizzie actually don’t do anything specific. But it’ll make your life easier if you want to use vizzie modules in the Max for Live context.

Dec 08 2010 | 7:25 pm

Thanks, Emmanuel.

Was that clear?


pid
Dec 08 2010 | 7:29 pm

yes very! i get it now… thanks.

Dec 09 2010 | 12:12 pm

#0 is a way to give specific names to objets within a subpatch to avoid interferences between multiple instances. However as it implies random numbers

I don’t think, that #0 is generated randomly…it should be perfectly unique for every open patch (but could well be different every time a patch is opened).

Dec 09 2010 | 5:02 pm

#0 value starts at 1000 or something, and each time a new abstraction requires it, the value is incremented. So unless you have the habit to give names of your send/receive (and whatnot) object which start with a number >1000 you are safe.

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

Forums > MaxMSP