Controls that are assigned to a Panel are hidden by the Panel itself.

Question

MIDI Target Manufacturer(s): Yamaha

Recently I decided to investigate a bit more in creating panels to get more controls onto my layout without making it look too messy at some point. My goal was to have panels appear above other controls and use a switch to only bring them up when I need them. But I first couldn’t get the panel to appear above other controls that are not part of the panel but below the controls that belong to it. Panel set to „Always in Back“ results in the bad looking behavior shown in the image. If this is turned off the panel covers the controls that are part of it.

Whilst trying out different things I figured out that I have to turn off „Always in Back“ BEFORE adding controls to it. Then I get what I want. BUT: as soon as I just like to change the size of the panel or even just change the position slightly , the panel again hides my controls and I again have to un-assign all controls before I can assign them again. The video shows what happens.

0:52 shows exactly how it should work - even after re-positioning or re-assignments. 

Images

Image 1

Comments

Dan, Thanks for the response. For my second use case I am currently looking at using MidiFire to loopback the On/Off buttons from Output to Input and using input rules to change the midi output from the Foot Pedal to control the selected knob. I hadn't considered using Channel changers. I will add a QA question for a feature.

Don

---

Thanks so much for realizing this fix quick. I am on vacation right now so will be on board again a little later.

---

Release is out. I spent some time with QA checking out various edge cases, and... seems better in all ways. Thanks again for pointing this out in such a tangible way, and thank you EVERYBODY for the detailed, respectful conversation.

---

Are you referring to the release of 2.251?

---

Yes, and only the original issue

Answer 1

Fixed in Release 2.251 (2021-08-01)

We've got a fix in Beta now. The fix is simple:

1. Stack member controls above their grouping panels
2. Ignore "always in back" for grouping panels that have member controls

However, the fix takes care of most concerns. With the two actions that MD always uses, applied to grouping panels, a user can do most anything:

1. Touch a control to bring it to front
2. Send it back via "send to back"

Users should remember that Design Locks on iPad are extremely helpful here. 

NOTE: On iPad, panels that span pages from the left can't be behind panels that are on the right page.

Answer 2

Fixed in Release 2.251 (2021-08-01)

We've got a fix in Beta now. The fix is simple:

1. Stack member controls above their grouping panels
2. Ignore "always in back" for grouping panels that have member controls

However, the fix takes care of most concerns. With the two actions that MD always uses, applied to grouping panels, a user can do most anything:

1. Touch a control to bring it to front
2. Send it back via "send to back"

Users should remember that Design Locks on iPad are extremely helpful here. 

NOTE: On iPad, panels that span pages from the left can't be behind panels that are on the right page.