switchable user interface without bpatcher offset?


    Jun 13 2006 | 10:07 am
    Hi,
    I am using max/msp to create a user interface. The interface has an area in which I want to show a different patch depending on a selection from a popup menu.
    I looked at bpatcher, and in the help there is an explanation how to do what I want, by creating a patch and embedding the different subpatches in it using bpatcher objects, and then using an offset message in the main patch to show the relevant subpatch.
    This seems to work, but I find it a little bit of a hack and I'm wondering if there is no way to send a message somewhere to make bpatcher open a patch and just display it, without having to use offset messages?
    Any other suggestions on how to solve this user interface problem are more than welcome of course.
    Thanks! Bert

    • Jun 13 2006 | 10:32 am
      Haven't done this myself, but the (an?) answer seems to lie in scripting - have a look at Max tutorials 46 and 47.
      Daniel
    • Jun 13 2006 | 10:38 am
      See [pcontrol], [thispatcher] etc.
      _____________________________ Patrick Delges
      Centre de Recherches et de Formation Musicales de Wallonie asbl http://users.skynet.be/crfmw/max
    • Jun 13 2006 | 10:41 am
      thanks a lot for the hint! i'll have a look at those tutorials and see if I can get it working...
    • Jun 13 2006 | 11:16 am
      On 13 Jun 2006, at 11:07, bert wrote:
      > This seems to work, but I find it a little bit of a hack and I'm > wondering if there is no way to send a message somewhere to make > bpatcher open a patch and just display it, without having to use > offset messages?
      The current mechanism is probably less of a hack than the alternative you suggest, given when happens when patchers are opened and closed - think about data being saved, loadbangs/closebangs going off, DSP processing being interrupted, and so on. (There's probably a third alternative, along the lines of "open the following N patchers but display one at a time.")
      -- N.
      nick rothwell -- composition, systems, performance -- http:// www.cassiel.com
    • Jun 13 2006 | 11:24 am
      Others may have different opinions, and the suggestions others have mentioned are worth exploring, but I think the approach you outline below is actually the best one (despite its "hackish" feel).
      Dan
      -- Dan Nigrin Defective Records 202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X http://www.defectiverecords.com http://www.jackosx.com
    • Jun 13 2006 | 1:05 pm
      The offset message sounds nice to me. That said, you'll probably find something useful in Mat's various js objects. In fact, there's particularly one that may help. Don't remember exactly its name, but it helps to make tabs inside bpatcher. Very handy. Have a look at it :
      Julien.
    • Jun 13 2006 | 5:23 pm
      you can use thispatchers 'script replace' functionality to be able to dynamically load in any patch to the bpatcher:
      and again, there are many ways to do it. This one is pretty nice though, as it makes it very easy to add modules to your patch without having to do any work besides putting things in a folder. Would work the same for MSP~ objects as well. (this uses jitter). Also easy to daisy chain the module holders too, just make sure you name them properly.
      v a d e //
      www.vade.info abstrakt.vade.info