bpatcher's inspector recollection


    Sep 09 2007 | 9:22 am
    hi
    is there a way to have a bpatcher (object) remember the name of the
    bpatcher (patch) when this patch is not in the searchpath???
    __exemple: a friend sends me his patch - which uses bpatchers - but
    forgets to include the bpatcher's sub-patches. Or even more frequent,
    he sends the patch (as text), knows i have the sub-patches (but they
    are not in the generic max searchpath)
    when i open such a patch i can see (or not see!!) the missing
    bpatcher's sub-patches but have no way to know the name of the
    missing bpatcher's sub-patch
    __it would be nice if the inspector could keep the name of the
    missing sub-patch
    __on the same note, when loading a patch with a missing sub-patcher
    (inculded in a bpatcher) an error/warning message in the max window
    would be handy
    Or there is a way to have those??
    thanks
    kasper
    --
    Kasper T. Toeplitz
    noise, composition, bass, computer

    • Sep 09 2007 | 9:34 am
      oh, it's even worse:
      since yesterday I am trying to debug a friend's patch (sending
      back-forth new versions, by email)
      all things concerning his patch are in a separate folder
      (debug-folder), NOT in my max searchpath.
      when he sends me a new version (as text) and i copy this text from
      his email into max with "new from clipboard", it loses all trace
      (recollection) of the bpatcher's sub-patches to search; that is even
      when i save that patch in "debug-folder" and re-open it.
      the only way is to copy the text from the mail, save the text (with
      BBEdit in my case) in the "debug-folder", and then ONLY open it as a
      max patch....
      hummmmm, in those days of "new from clipboard" it does not seem very
      practical....
      best
      kasper
      >
      >is there a way to have a bpatcher (object) remember the name of the
      >bpatcher (patch) when this patch is not in the searchpath???
      >
      >__exemple: a friend sends me his patch - which uses bpatchers - but
      >forgets to include the bpatcher's sub-patches. Or even more
      >frequent, he sends the patch (as text), knows i have the sub-patches
      >(but they are not in the generic max searchpath)
      >
      >when i open such a patch i can see (or not see!!) the missing
      >bpatcher's sub-patches but have no way to know the name of the
      >missing bpatcher's sub-patch
      >
      >
      >__it would be nice if the inspector could keep the name of the
      >missing sub-patch
      >
      >__on the same note, when loading a patch with a missing sub-patcher
      >(inculded in a bpatcher) an error/warning message in the max window
      >would be handy
      >
      >Or there is a way to have those??