bpatcher2bpatcher messages


    Mar 23 2007 | 11:05 am
    offset message, in bpatcher, to [thispatcher] of bpatcher = works
    offset message, from root, to [thispatcher] of bpatcher = works
    offeset message, coming from _another bpatcher = does not work, even when the offset message is produced in root (fopr example by triggering a messagebox).
    does not work = weird drawing problem, old stuff isnt refreshed.
    whats up? bpatcher refreshes fine when offeset from root, but not when mouse is inside another bpatcher?
    -110

    • Mar 23 2007 | 1:25 pm
      I'm able to copy the behaviour you described. I've included the sample patch that I made below. Unexpected behaviour, since the message does seem to reach the correct bpatcher object, and it does work if you trigger the message anywhere else. Luckily I haven't come across this before.
      It's too bad that the bpatcher object is recently (at least, to me) showing some weird behaviour, especially since it is one of the very few ways to make a more complicated interface in Max.
      Let's hope Cycling finds the time to solve these problems and possibly add to the functionality of the bpatcher object: - A way to see only part of a subpatcher in a patch without having to use a separate file. - An option that makes the top left corner of a bpatcher the origin (0,0) when moving objects around using thispatcher.
      Other recent bpatcher problems:
      Main patch:
      Save as 'bpatch1':
      Save as 'bpatch2':
    • Mar 23 2007 | 1:47 pm
    • Mar 25 2007 | 8:50 am
      i am not "including", but i second your request about "unincluding".
      if we had that, maybe i would finally see some sense in "including" bpatchers? :)
      btw this is mac os classic - so it seems a persistent problem.
      funny thing is, i am 100% sure now that it is realy only a drawing (i.e. refreshing) problem - yet i solved putting a [pipe 0] into the controlling bpatcher. (like we are used to solve the common initialisation order problems.)
      i guess its to do with the mouseclick (in an [lcd], but it does not seem to matter), however its weird.
    • Mar 26 2007 | 4:28 pm
      Bas van der Graaff schrieb: > I'm able to copy the behaviour you described. I've included the > sample patch that I made below.
      Thanks, elsewise nobody else would have jumped on it
      > Unexpected behaviour, since the message does seem to reach the > correct bpatcher object, and it does work if you trigger the message > anywhere else. Luckily I haven't come across this before.
      I am sure you came across this before, it just looked different. Its the same reason as all the other bpatcher problems: redraw. If you send max a redraw command after the offset message, it will display correctly...
      Stefan
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()--------www.ccmix.com