Laurence Wilkins

There's a few aspects to this issue so bare with me as I try to explain.

I'm making a Max device where I have a bpatcher object which is both visible in the device's main presentation view but also can be opened as a separate pop up video using a button that sends a 'open' message to the pcontrol object connected to the bpatcher.

I'm able to do this fine, but the only problem is that when the separate bpatcher window pops up, it's possible for the user to resize the window however they please, meaning they can drag it down vertically to reveal max's large grey background area. This doesn't effect the utility of the device but is aesthetically quite ugly and also comes across quite unprofessional if I were to sell a device that behaved like this.

Unfortunately the usual 'thispatcher' messages that can be used for normal patchers dont seem to apply to bpatchers. On this point, I'm actually a little confused on what messages CAN be send to the thisdevice object which applies to bpatchers. The thispatcher reference says 'See the bpatcher help file for the use of the thispatcher object with bpatchers', but the bpatcher help file says absolutely nothign about the use of the thispatcher object. The only information about this in the max documentation is in the bpatcher reference (not the help file) where it describes to function of the 'replace' message for thispacher in bpatchers. It seems hard to believe that it really just is this one function that works in bpatchers, but if this is the case it'd be useful to know. I'll be contacting max directly to inform them of this apparent gap in their documentation.

I also tried the 'setdefaultpatcherheight' function as part of max scripting, but it turns out it has no effect on the CURRENT height of the max window. In fact, I couldn't really figure out what this function is really supposed to do, and it seems that these people had the same issue:

https://cycling74.com/forums/global-message-very-easy-message

I'm making a Max device where I have a bpatcher object which is both visible in the device's main presentation view but also can be opened as a separate pop up video using a button that sends a 'open' message to the pcontrol object connected to the bpatcher. 

I'm able to do this fine, but the only problem is that when the separate bpatcher window pops up, it's possible for the user to resize the window however they please, meaning they can drag it down vertically to reveal max's large grey background area. This doesn't effect the utility of the device but is aesthetically quite ugly and also comes across quite unprofessional if I were to sell a device that behaved like this. 

Unfortunately the usual 'thispatcher' messages that can be used for normal patchers dont seem to apply to bpatchers. On this point, I'm actually a little confused on what messages CAN be send to the thisdevice object which applies to bpatchers. The thispatcher reference says 'See the bpatcher help file for the use of the thispatcher object with bpatchers', but the bpatcher help file says absolutely nothign about the use of the thispatcher object. The only information about this in the max documentation is in the bpatcher reference (not the help file) where it describes to function of the 'replace' message for thispacher in bpatchers. It seems hard to believe that it really just is this one function that works in bpatchers, but if this is the case it'd be useful to know. I'll be contacting max directly to inform them of this apparent gap in their documentation. 

I also tried the 'setdefaultpatcherheight' function as part of max scripting, but it turns out it has no effect on the CURRENT height of the max window. In fact, I couldn't really figure out what this function is really supposed to do, and it seems that these people had the same issue:
https://cycling74.com/forums/global-message-very-easy-message

Hi Max users, 
There's a few aspects to this issue so bare with me as I try to explain.
I'm making a Max device where I have a bpatcher obje

how-to-fix-presentation-window-size-for-bpatcher-pop-ups

I don't think that bpatcher is meant to be opened using pcontrol

retaining all functionality of the patcher window controls.

Thispatcher object is not functional in bpatcher window

At least it used to be so last time I tried it in max 6.

I'd tink only option would be to use both -

visible bpatcher and patcher which would get opened using pcontrol.

It is only a matter not to double it completely, 

if that is max4live device that could create chaos for automation.

I don't think that bpatcher is meant to be opened using pcontrol
retaining all functionality of the patcher window controls.
Thispatcher object is not functional in bpatcher window
for sending any "window" messages.
That works only for patchers.
At least it used to be so last time I tried it in max 6.
------
I'd tink only option would be to use both -
visible bpatcher and patcher which would get opened using pcontrol.
It is only a matter not to double it completely, 
if that is max4live device that could create chaos for automation.



Just to be clear are you suggesting that I just make two copies of the subpatch, one in a bpatcher object and one in a normal patcher?

Hey dude thanks for your reply
Just to be clear are you suggesting that I just make two copies of the subpatch, one in a bpatcher object and one in a normal patcher?

That's what I would do, only I don't know if you need

all objects and GUI in both bpatcher and patcher,

and also how to try to avoid having all doubled...

What is the purpose of opening the bpatcher as separate window ?

That's what I would do, only I don't know if you need
all objects and GUI in both bpatcher and patcher,
and also how to try to avoid having all doubled...
What is the purpose of opening the bpatcher as separate window ?


because it's quite detailed and has a lot of small live.num boxes which can be hard to read on the normal m4l interface, so by opening up the separate window you can see it bigger

I am afraid in that case you will have to accept bpathew window as is,

or try to make subpatcher is such a way that it only works as "remote"

GUI for bpatcher, to avoid doubled parameter storage and automation.

One would probably want to use send/receive for that many elements.

If one uses several device instances, one prepends

but I am not Live user, and so can't offer better help with that.

I am afraid in that case you will have to accept bpathew window as is,
or try to make subpatcher is such a way that it only works as "remote"
GUI for bpatcher, to avoid doubled parameter storage and automation.
One would probably want to use send/receive for that many elements.
If one uses several device instances, one prepends
--- to s/r addresses to make them unique
but I am not Live user, and so can't offer better help with that.


How to fix presentation window size for bpatcher pop ups