Toggling container "where"

[gurulogic]

This is going to be a bit hard to explain as the sum of the parts that make this work are quite complex, but I'll try as simply as I can. I have 16 patches in a rack that are individually activated / deactivated via MIDI. When I activate the patch via MIDI, the Combobox which indicates between 1-16 the position of the patch in the rack, and the BANKA input bus have a matching value, the visibility of the container should be toggled from invisible to interface builder.
This often works and used to work better, but as I have been expanding my workspace it is working less and less reliably and sometimes I have to toggle between two "banks" to get the containers for the patch to show, and I cannot do this when playing..

I guess I'm hoping without trying to explain the intricacies of this setup someone might have method for how to make this concept work more reliably. "Bank" select via MIDI to activate patch and show patch contents in interface and at the same time make the disabled patch interface invisible.
I'm also wondering if maybe it is more a GPU memory issue seeing as the issue has progressed over time?
Sorry if this is really just vague shot in the dark..
This one thing is really making me miss the v5 grid concept.

[nay-seven]

tweaking the where option in real time is not always a good idea,
you can add a patch settings module and link your banka bus to its inlet minimized ?

[woodslanding]

is there a way to hide/show things in the IB without using 'where'??

Mostly it works fine. But if I am scrolled in IB, and make a container visible, it comes up wrong.

[gurulogic]

Hmm. ok. That seems like a good idea,wish I thought of it sooner! Only concern is that when a patch is inactive on the top level, no data gets in or out so it seems like I will have to tweak with timings of my patch activate/deactivate mechanism a bit, or switch to a activate patch module approach. I do assume that the patch still uses some CPU unless deactivated from the top level so maybe a problem with a large amount of patches? Or maybe it is better for this purpose if I do many sub patches in one larger patch? So many ways..!

[gurulogic]

Realizing the mass amount of repatching I will have to do to adapt my workspace to nay-seven's approach, I don't have time this week but did come up with a hack for the meantime. A switch connected to the send bus that selects the visibility. When the container does not appear, I toggle the visibility with the switch. It works for now..

[gurulogic]

Hello, I am revisiting this idea but cannot find any "minimized" or similar pin on the patch settings module?
I presumably could achieve a similar result with the heightpc inlet, but not sure if this would be recommended for realtime manipulation?