Send via "$1 message" undocumented behavior

Apr 6, 2006 at 6:16pm

Send via "$1 message" undocumented behavior

I’ve grown frustrated with a Max weakness involving sending using the
“; DestName $1″ method. Without extra work, it is only a “send”
object replacement for ints and floats. All other types need to be
prefixed with symbol. This is sort of messy.

I’ve stumbled across a solution that is simpler from some points of
view. By using $2 instead of $1, and prepending a dummy argument to
the thing that you want to send, all types get sent without doing
anything different to different types of data. This is a little ugly,
too, but has the advantage being able to treat different data types
the same. I haven’t found any documentation that says this should
work, but it seems to work fine.

I wish that send worked like receive in the way that you change arguments.

-C


Chris Muir | “There are many futures and only one status quo.
cbm@well.com | This is why conservatives mostly agree,
http://www.xfade.com | and radicals always argue.” – Brian Eno

#25267
Apr 7, 2006 at 6:42am

Have you checked out “forward”?

Best,
Trond

#74224
Apr 7, 2006 at 7:23am

At 8:42 AM +0200 4/7/06, Trond Lossius wrote:
>Have you checked out “forward”?

I hadn’t, actually. Very useful. I wonder what version of Max it appeared in?

Thanks,
-C


Chris Muir | “There are many futures and only one status quo.
cbm@well.com | This is why conservatives mostly agree,
http://www.xfade.com | and radicals always argue.” – Brian Eno

#74225
Apr 7, 2006 at 7:34am

I believe it has been around for quite a while, but it seems to
attract less attention than other objects.

Best,
Trond

#74226
Apr 7, 2006 at 8:08am

On 7-Apr-2006, at 9:23, Chris Muir wrote:

> I hadn’t, actually. Very useful. I wonder what version of Max it
> appeared in?

Probably the first version Gregory wrote the documentation for.-

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine +–> Litter Power & Litter Bundle for Jitter

iCE: Sequencing, Recording & |home | chez nous|
Interface Building for |bei uns | i nostri|
Max/MSP Extremely cool http://www.castine.de

http://www.dspaudio.com/

#74227
Apr 7, 2006 at 9:12am

Chris Muir wrote:
>>Have you checked out “forward”?
>
> I hadn’t, actually. Very useful. I wonder what version of Max it appeared in?

also check pattrforward it arrived just recently and it will make you
get rid of a lot of receives by sending the data directly to a named
object… even more usefull. (Thanks a lot Jeremy! and who ever
suggested it before)

Stefan

[][] [][][] [][] [][][]
[][][][][][][][][][][][][][][]

Stefan Tiedje
Klanggestalter
Electronic Composition
&
Improvisation

/~~~~~
\ /|() ()|
))))) )| | |( \
/// _/)/ )))))
___/ ///

————————-x—-
–_____———–|———–
–(_|_ —-|—–|—–()—-
– _|_)—-|—–()———–
———-()————x—–

14, Av. Pr. Franklin Roosevelt,
94320 Thiais, France
Phone at CCMIX +33-1-57 42 91 09

#74228
Apr 7, 2006 at 4:38pm

At 9:34 AM +0200 4/7/06, Trond Lossius wrote:
>I believe it has been around for quite a while, but it seems to attract less attention than other objects.

I guess that that’s what I get for being away from Max for a long time. Since I mostly learned Max before it was released, many of these new-fangled objects have passed me by.

-C


Chris Muir | “There are many futures and only one status quo.
cbm@well.com | This is why conservatives mostly agree,
http://www.xfade.com | and radicals always argue.” – Brian Eno

#74229
Apr 7, 2006 at 4:42pm

At 11:12 AM +0200 4/7/06, Stefan Tiedje wrote:
>also check pattrforward it arrived just recently and it will make you get rid of a lot of receives by sending the data directly to a named object… even more usefull. (Thanks a lot Jeremy! and who ever suggested it before)

I wish I could use the whole pattr* family, but the project that I’m currently maintaining is stuck in OS 9, at least for a while longer.

-C


Chris Muir | “There are many futures and only one status quo.
cbm@well.com | This is why conservatives mostly agree,
http://www.xfade.com | and radicals always argue.” – Brian Eno

#74230

You must be logged in to reply to this topic.