Lewis Wolstanholme

I've built a M4L device containing multiple bpatchers. I'm using [pcontrol] to open the bpatchers in an external window, but when I do this I can't interact with the UI properly. My interactions are making changes, but the changes aren't being displayed as one would expect. If I change a [slider] for example, the new value isn't displayed, even though its output has affected the non-UI elements of the patch. Curiously, any ppatchers within the bpatcher that are opened using another [pcontrol] do not share this issue.

I could forgo this issue and use only embedded ppatchers, however my patch revolves around the 

 script used with bpatchers. This was a compromise, as regular, 

 scripting doesn't seem to work with .maxpats. Although creating the .maxpats wasn't an issue, I was unable to use the 

 script with any object that wasn't a .mxo. If anyone can give me any information on scripting with .maxpats, this would also solve my problem.

I've built a M4L device containing multiple bpatchers. I'm using [pcontrol] to open the bpatchers in an external window, but when I do this I can't interact with the UI properly. My interactions are making changes, but the changes aren't being displayed as one would expect. If I change a [slider] for example, the new value isn't displayed, even though its output has affected the non-UI elements of the patch. Curiously, any ppatchers within the bpatcher that are opened using another [pcontrol] do not share this issue. 

I could forgo this issue and use only embedded ppatchers, however my patch revolves around the replace script used with bpatchers. This was a compromise, as regular, newobject scripting doesn't seem to work with .maxpats. Although creating the .maxpats wasn't an issue, I was unable to use the connect script with any object that wasn't a .mxo. If anyone can give me any information on scripting with .maxpats, this would also solve my problem. 

I've built a M4L device containing multiple bpatchers. I'm using [pcontrol] to open the bpatchers in an external window, but when I do this 

UI problem with bpatchers within a M4L device