Conditional switches


    Sep 26 2006 | 11:08 pm
    I'm currently working on an installation where i want
    only certain switches in the interface to be
    selectable at a time.
    When one switch is pulled it makes itself unselectable
    and makes the just the switch set below it selectable.
    Can anybody help me?
    Do You Yahoo!?
    Tired of spam? Yahoo! Mail has the best spam protection around

    • Sep 27 2006 | 8:52 am
      Do you mean switches in real life or on max itself? either way you probably want to be looking at the gate object. You could have it so that pulling switch a will open a gate giving access to B and C. or Switch would work under a similar princible.
      As for making the top switch unselectable, you could probably use mypatcher inside max to make it invisible once on or in real life could probably use another gate to stop it doing the on and offing. Let me know if you need further assistance - maybe post a patch?
      T
    • Sep 27 2006 | 9:16 am
      If you use matrix~ or router, (depending on whether you're switching signals or control data) instead of gate~/gate or selector~/switch, then you can use matrixctrls, which allow you to enable/disable individual cells,
      cheers
      Roger
    • Oct 22 2006 | 5:08 am
      Indeed, to follow up, is there a way to send "enable" / "disable" messages to interactive objects? Like selecting "Ignore Click" / "Respond to Click" in the drop-down, but instead, having these options available and changeable in runtime by the user? (I know some objects support this, but certainly not all.)
      We can do "Can't Change" in number boxes using the right flag message, but that seems to be the extent of it.... for most objects, anyway. An "active" / "inactive" message would be great for lots of objects, most notably the toggle....
      --CJ
    • Oct 22 2006 | 8:40 am
      This is indeed annoying in Max. Only some UI objects, like
      [radiogroup], understand an "inactive $1" message. For the others, if
      you want a nice interface, you have to change their color with color
      messages (using light grey rather than black, etc.), which is btw not
      always possible (as with [toggle]), and ask them to ignore clicks with
      a small script (see [thispatcher]'s help).
      In the case of [toggle], if you want to change its color, then you can
      use a [bpatcher] and move its contents to a place with a picture that
      represent a [toggle] in a diffferent color (you'll have to draw it
      yourself). Or use [jsui], or maybe Imageburger?
      p
    • Oct 22 2006 | 9:07 am
      check out jasch's MTX object.
    • Oct 22 2006 | 12:51 pm
    • Oct 23 2006 | 5:54 am
      Seejay James wrote:
      > Indeed, to follow up, is there a way to send "enable" / "disable"
      > messages to interactive objects? Like selecting "Ignore Click" /
      > "Respond to Click" in the drop-down, but instead, having these
      > options available and changeable in runtime by the user? (I know some
      > objects support this, but certainly not all.)
      They are, all inspectors are patches, you can open them and find out how
      they do their magic. Then copy the methods...
      > We can do "Can't Change" in number boxes using the right flag
      > message, but that seems to be the extent of it.... for most objects,
      > anyway. An "active" / "inactive" message would be great for lots of
      > objects, most notably the toggle....
      like the lower button? - hey this is Max, just do what you need...
      And the toggle is simple but ugly, if you think of users, just create
      something more pleasant with all the features you need, put it into a
      bpatcher and save it as prototype. This will be better than anything
      cycling could come up with, you have to do it anyway...
      --
      Stefan Tiedje------------x-------
      --_____-----------|--------------
      --(_|_ ----|-----|-----()-------
      -- _|_)----|-----()--------------
      ----------()--------www.ccmix.com
    • Oct 24 2006 | 7:19 am
      Holy cow! I'm an idiot, of course, there it is in thispatcher, ignore/respond. I think I've even probably used it before. Damn this failing brain...
      The bpatcher button/toggle/indicator idea is great. Should have done this months ago. Made it usable through clicking or as an indicator (like in a beat grid)... and user can control colors. Nice!
      -CJ