bpatcher not a'common' object or... ?

Learn about building and using Max for Live devices.
Post Reply
pukunui
Posts: 405
Joined: Thu Jan 29, 2009 10:26 pm
Location: Los Angeles

Re: bpatcher not a'common' object or... ?

Post by pukunui » Mon Aug 16, 2010 6:33 pm

Yeah the docs do seem to be wrong/inconsistent in this case.

Usually, people set bpatcher UI state with the offset message. It's like you are scrolling the patch inside the bpatcher. If you want it to be "hidden", scroll it to a blank part of your patcher.

The Loopshifter device contains an example of how to do tabbed UI displays using bpatcher.

-A

bronswerk
Posts: 8
Joined: Wed Mar 17, 2010 9:10 pm

Re: bpatcher not a'common' object or... ?

Post by bronswerk » Mon Aug 16, 2010 7:50 pm

But you can hide/show several bpatchers.

Send a message to thispatcher like:

"script sendbox bpatcherNameHere hidden 0" or
"script sendbox bpatcherNameHere hidden 1"

to hide or unhide the bpatcher.

Post Reply