rBrooklyn

When in presentation mode you could create and choose from multiple presentations of the patch!

This came up while I was making different control / dial sets for the same underlying programming, a small version and a large version of the same device, for ex.

I know there are ways to achieve this now, using subpatchers, b patchers, different control sets... etc, but having having multiple presentations sure would be simple and elegant time saver! When creating a b patcher you could choose which presentation of the orig patcher you are looking at.

Perhaps one of you folks already knows how to do this?

It sure would be nice if:
When in presentation mode you could create and choose from multiple presentations of the patch!

I know there are ways to achieve this now, using subpatchers, b patchers, different control sets... etc, but having having multiple presentations sure would be simple and elegant time saver!  When creating a b patcher you could choose which presentation of the orig patcher you are looking at.

Perhaps one of you folks already knows how to do this?
- r


multiple-presentations-in-presentations-mode-for-one-patch-sure-would-be-nice

Nice idea. Though I often have trouble coming up with one UI that works!

There is some functionality like this with [thispatcher], check [p sendbox] in the helpfile. Not exactly simple to do on a large scale though.

Nice idea. Though I often have trouble coming up with one UI that works! 

There is some functionality like this with [thispatcher], check [p sendbox] in the helpfile. Not exactly simple to do on a large scale though.


What if you put the processing part in one subpatch that is controlled via send/receive objects. Then you make a parent patch with several sub patches, each containing a different layout. The receive object in the processing part will only receive the last value from the button you manipulated. Here is an example.

very interesting ideas... still a little complicated for me.

thinksamual - i noticed with that approach -- b/c the controls in each subpatch are actually different objects -- a change doesn't update the controls in the other patches.

i had worked on some remote control type of stuff like this involving two way communication between the different controls using s/r and sw objects but it gets unwieldily very fast, a lot of s/r names to keep track of. not really worth it to me and probably a little beyond my current skills to do well.

i'm always looking for ways to reach my goal more economically and gracefully, having multiple presentation views would certainly do this for me. I can imagine there may be some complications I don't see that would make this difficult to program and use... I"m starting to get a handle on using Max, but I've got a long way to go.

very interesting ideas... still a little complicated for me. 

 thinksamual - i noticed with that approach -- b/c the controls in each subpatch are actually different objects -- a change doesn't update the controls in the other patches.
i had worked on some remote control type of stuff like this involving two way communication between the different controls using s/r and sw objects but it gets unwieldily very fast, a lot of s/r names to keep track of.     not really worth it to me and probably a little beyond my current skills to do well. 

i'm always looking for ways to reach my goal more economically and gracefully, having multiple presentation views would certainly do this for me. I can imagine there may be some complications I don't see that would make this difficult to program and use... I"m starting to get a handle on using Max, but I've got a long way to go. 

For folks stumbling upon this post, this thread also has some interesting ideas:

https://cycling74.com/forums/multiple-interfaces-bpatcher-and-offset/

For folks stumbling upon this post, this thread also has some interesting ideas:
https://cycling74.com/forums/multiple-interfaces-bpatcher-and-offset/


What I'm looking for is an elegant solution to having different presentation views of the same objects within an abstraction/subpatch/yada, and be able to choose which presentation view one sees when using an instance of it..

Presentation View 1: knob_1, knob_2, number_box _1 and number_box_2 can be seen, all large and blue.

Presentation View 2: number_box _1 and number_box_2 are seen, both small and transparent.

I could use View 1 as a subpatch in a patch that monitored input for say a bluetooth sensor.

I could use View 2 as a subpatch in a patch that was a display of this sensor data.

Obv this is a simplified example, but in my imagination even for complicated sub patches the data and controls are fewer, simpler and elegant. Fewer functionally redundant patches with slightly different views of the same thing, more results per hour of work.

Most of the approaches to this I've found so far involve the complicated setup of different objects controlling each other.

For ex:
Presentation View 1: knob_1, knob_2, number_box _1 and number_box_2 can be seen, all large and blue.
Presentation View 2: number_box _1 and number_box_2 are seen, both small and transparent. 

I could use View 1 as a subpatch in a patch that monitored input for say a bluetooth sensor.
I could use View 2 as a subpatch in a patch that was a display of this sensor data. 

Obv this is a simplified example, but in my imagination even for complicated sub patches the data and controls are fewer, simpler and elegant. Fewer functionally redundant patches with slightly different views of the same thing, more results per hour of work.  

Multiple Views of Presentation Mode - sure would be nice!