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


    Sep 07 2009 | 1:34 pm
    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

    • Sep 07 2009 | 5:03 pm
      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.
    • Sep 07 2009 | 6:57 pm
      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
    • Sep 07 2009 | 9:09 pm
      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.
    • Sep 14 2009 | 12:16 pm
      Considering the fact that i had no response from cycling in a week on this thread, i assume this is not a feature...
      g
    • Sep 15 2009 | 1:58 am
      ... also, if you double-click the [s myvar], it comes up with the usual list of s's & r's, containing "value myvar"...
      ????
    • Sep 16 2009 | 7:57 am
      it's still there in max 5.0.8...