Peter Ostry

I have a line of tabs at the top and want to show different things below them. Straight forward. Tab #1 shows some settings, tab #2 the instrument parameters, tab #3 the effects and so on.

But how do I make this with bpatcher? Really everything in one single bpatcher? This would require a huge "mother patcher". Is it not possible to load different patches on demand or is there another technique I am not aware of?

tabs-and-bpatcher-howto

I had to deal with this in my "Gyre" program. 

The tabbed section is made up of a bunch of child patchers that all have the same size presentation area. I include all these in an intermediate patch as bpatchers, with the X dimensions aligned, and the Y dimensions one height apart.

I include the intermediate patch as a bpatcher in the parent patch, and make it the same size as the presentation area of the child patchers. Now I can send the intermediate patcher messages that select the different sections, and the intermediate patch manages the offset messages to thispatcher that bring the different child patchers into focus. The intermediate patcher also enables/disables things as appropriate based on what child patch is in focus.

I had to deal with this in my "Gyre" program. http://www.xfade.com/Gyre

I include the intermediate patch as a bpatcher in the parent patch, and make it the same size as the presentation area of the child patchers. Now I can send the intermediate patcher messages that select the different sections, and the intermediate patch manages the offset messages to thispatcher that bring the different child patchers into focus. The intermediate patcher also enables/disables things as appropriate based on what child patch is in focus.


If I understand you right you talk about nested bpatchers. On top are the tabs and one bpatcher. This bpatcher contains a patch with several bpatchers. Is this correct? At least I tried and it works.

This is a surprisingly simple solution, I love it. Are there any memory or CPU problems with nested bpatchers, I mean, should I rather avoid to let them talk to each other under the hood?

Yes, that's what I was trying to say. I haven't found any performance problems with this implementation.

Yes, I've also done a tabbed interface with nested bpatcher's and it worked very well, no performance issues.

you've obviously found a very elegant solution, but doesn't the "even more" subpatcher in the bpatcher help patch demonstrate something useful along these lines?

if nested bpatchers can be a performance problem really depends on the

content of the bpatchers and on your computer.

it IS definetly a lot slower but you might not see it at all in your situation.

also, building it one by one still does not get rid of the problem that the main

bpatcher will habe lots in and outs .. eventually too lots.

it is one of the exceptions where i tend you use send and receive.

if nested bpatchers can be a performance problem really depends on the
content of the bpatchers and on your computer.

also, building it one by one still does not get rid of the problem that the main
bpatcher will habe lots in and outs .. eventually too lots.

Tabs and bpatcher – howto?