Mira bpatcher support
Robin Parmar
3月 04 2017 | 10:52 午後
When I build an app of any complexity, I try to follow best practice for separating interface and algorithm (a pragmatic approach to MVC). This means that my interface elements are in one or more [bpatcher]. If I apply [mira.frame] to the presentation view, none of these show up. If the frame is in the abstraction itself, these show up, but take up an entire tab on the browser.
Just wondering as to the likelihood of seeing support for the parent view of [bpatcher] in the future?
-- Robin Parmar
Jeff Podolski
3月 10 2017 | 2:31 午後
bpatcher support was "next on the list" in 2013, I wouldn't get your hopes up...
Max Gardener
3月 10 2017 | 2:34 午後
Using the Presentation Mode to organize your interface/processing works fine *and* plays well with Mira, of course....
Wetterberg
3月 10 2017 | 11:16 午後
@Max, what do you mean by this? It seems to not respond to Robins request?
@Robin I support this wish as well. Right now I have had to add additional inlets to all my bpatchers that let me essentially make a redundant gui outside the bpatcher. It's somewhat frustrating, as bpatchers really are best practice in max...
However, and partly in response to @jeff, I'm hopeful that they'll get around to it, since there's actual, multi-person, active development of mira now, as well as quite a lot of user support of the project. (I'm playing my 3rd show with a large touch screen on monday! :) )
Max Gardener
3月 11 2017 | 1:12 午後
I could certainly have been clearer, I think: I tend to create very large patches and either use the Presentation Mode to handle the UI, or I send UI outputs into inlet of a bpatcher. I started doing both those things back when the Presentation mode appeared, and haven't ever really had a problem. Of course I've never felt the need or desire in any way to port my performance patch to an iPad, so perhaps this is not helpful "advice." I was responding to the question with the workaround I've traditionally used. That's all, really.
Wetterberg
3月 12 2017 | 10:42 午前
Ah, gotcha. Your advice can certainly be brought into my own workflow, now that we have snippets. That will let me retain the modularity in the UI section as well. Thank you so much for the clarification, Max. It's been a bit of an eye opener, actually.
Robin Parmar
3月 14 2017 | 11:35 午後
Yes, a workaround to interfaces not working in a [bpatcher] is to not put interfaces in a [bpatcher]. Which amounts to not using them at all, since that's what they are for!
However, this immediately means that you cannot create modular interfaces. I think it's bad practice.
Nicolas Deflache
4月 25 2017 | 11:27 午前
At first, I also thought that it would be nice that Mira shows bpatcher contents. Then I tried several things and now I think differently. In my opinion, it would not be that flexible.
When using a Mira interface, you need to build a specific GUI. It is interesting to show parameters from different patches in Mira.
Here is how I'm doing it.
Nicolas
tillfly
9月 05 2019 | 9:41 午前
Hey together,
is there a workaround to show a lcd object in MIRA to display painted graphics?
exeterdown
1月 10 2020 | 11:45 午後
Wow, thank you Nicolas!
I spent a good while trying to unpack and understand how you'd done this - I'm not that deep into pattr, but this actually taught me some really useful stuff - especially about how to use the :: argument.
I knocked up this simpler version of the patch above for those - like me - who are much greener:
Nicolas Deflache
1月 11 2020 | 4:46 午後
Clean explanation of my example, thank you Exeterdown !
ernest braun
6月 14 2024 | 4:36 午前
Thank you Nicholas and Exeterdown! I came across this recently and it has been very interesting.
In addition to your solution, I also realized that instead of attempting to include the [mira.frame] object on the level of the parent patch that has your final presentation layout, you can simply add the [mira.frame] object into the original patch of what will become your bpatcher. When you load the bpatcher into a parent patch, the mira.frame will still appear on your mobile device.
Of course, the scope of the Mira.frame will not expand beyond that bpatcher, but you can have multiple Mira tabs to include different parts of your presentation UI.