What's the link between send/receive and value ?

Guillaume Evrard's icon

hi maxers,

i'm wondering what's the link between the s/r objects and the v object. sending something into a 's' object doesn't modify the same-named 'v' object content. but it seems to be another relation i don't understand.

here is a patch to demonstrate what i say.

cheers.

g

Max Patch
Copy patch and select New From Clipboard in Max.

Peter Castine's icon

You can probably best think of it as two different namespaces (although I'm not entirely sure that that's what Max is doing internally).

Basically, s/r has nothing to do with value.

Guillaume Evrard's icon

hi peter,

i thought s/r & v had nothing to see, but apparently s/r keep in memory the v content somewhere...

what do you say at c74 ?

thanks,

g

johnpitcairn's icon

I think you may have found a semi-bug.

If you repeat the test without the send in the patch at all, there is no retained value (in Max 4 or Max 5).

So it looks like having a send object named the same as a value object still binds the current value to that name even when the last instance of value is deleted.

Funky.

Guillaume Evrard's icon

Considering the fact that i had no response from cycling in a week on this thread, i assume this is not a feature...

g

Zh's icon

... also, if you double-click the [s myvar], it comes up with the usual list of s's & r's, containing "value myvar"...

????

Guillaume Evrard's icon

it's still there in max 5.0.8...