Reset to Defaults ignores exclude flag

Question

I am using a "Reset to Default" button on the main page of my multi-page layout to let all controls on all pages send their default values. This basically works fine.

However, on some of my other pages I have some buttons that I don't want to send their default values when the "Reset to Default" button is tapped. Thus, I toggled the "Advanced > Reset to Defaults - Exclude" button for these buttons.

Unfortunately, this does not work - they still send their default values when the "Reset to Default" button is tapped.

Is this a bug, or is it just me not understanding what "exclude" means here? Thanks.

Comments

Sorry for the delay, was off-grid. Sounds like a bug. I'll log it and have a look. Can I add you to the beta team? It will NOT overwrite your production MIDI Designer version.

---

Sure thing. Just let me know off-list if you need my Testflight account or whatsoever. Thanks.

---

I'm thinking of overhauling this while I'm here. Why should a control send its default value if it's already at its default value (and why would it send anything else during the process)?

---

I strongly believe that a control should send its default value even if it's already at its default value. I am sure that users will not engage "Reset to default" only to reset the visual state in MD, but also to force the connected synth to the same default state, which is not a given when the control in MD shows the default state. Reset to default is a great feature to kind of sync both MD and the synth to the same default state.

---

Glad I asked!

This bug will be fixed as stated in the next beta, coming in about 10 minutes. Thanks.

---

Thanks much. Will test the beta and will let you know of any issues asap. Cheers!

---

Fix is confirmed in beta and will be out with next release, thanks. Please remind me to change the category on this question when that happens, please!