Talk to other MIDI Designer users about MIDI Designer, iOS MIDI and related topics. Or share layouts, pages, and ideas.

Also check out the Facebook Group.

Of course, if you want to send us an email, feel free.

MIDI Designer
Design your perfect MIDI controller for iPad, iPhone and iPod touch.
Possible to have "classic" radio buttons? (one and only one always active) - MIDI Designer Q&A

Possible to have "classic" radio buttons? (one and only one always active)

+1 vote
asked Feb 13, 2013 in Suggestions (Already Implemented) by audios (290 points)
recategorized May 2, 2014 by MIDI Designer Team (Dan)
Thanks for bringing this suggestion over from YouTube. Just to understand: can you describe the case in which you need this, please?

Best!
Dan
I use MIDI Designer (MD) on an iPad with rtpMIDI to make MIDI events available on my (sorry!) PC DAW. I have a pile of SW such as Sonar X1, Sibelius, Vienna Ensemble Pro (amazing SW), and lots of VST instruments, and some MIDI HW such as an RME Fireface (best gear ever made), MX300, SansAmp, vDrums, and keyboards. Things get very complicated at times but I don’t want to sit at my computer to create music; I want to sit with an instrument and use my iPad and FC-300 to control my gear.

When I’m playing, I rely on Bome MIDI Translator (MT) (www.bome.com/products/miditranslator) to route and translate MIDI messages coming from my MD GUI and FC-300. For instance, I use MT to convert a single MD-generated message into multiple Program Change messages (one per HW and SW effects unit) to get a particular combination of patches. I can also have MT start up new programs, create Windows WM_Messages (very powerful) to control media player volume, etc. So, MD+MT = killer combination!

More specifically, I’m using MD radio buttons to trigger a pile of actions and if I accidentally press a radio button twice in a row, not only do I lose the visual feedback of what state my gear is in (not good when I’m not looking at my computer screen), the duplicated MIDI message can trigger anything from combinations of patch changes being reset (after I’ve tweaked them and haven’t saved them) to second instances of programs firing up.

I can handle the redundant MIDI messages using MT but the messages do complicate things. My preference would be that the second push of a highlighted radio button does absolutely nothing because the simpler MD behaves, the simpler everything else becomes.

Something of an aside: given that there seems to be endless requests for all kinds of new MD options on the forum, which could make its GUI extremely complicated over time, I can’t help but think there’s a big design decision down the road at some point; i.e. at what point do the tools for designing the visual aspect of a GUI need to be separated from the tools for specifying the GUI’s behavior? The visual design is best handled graphically but the latter requires a programming language if arbitrary behaviors are to be made available. Come to think of it, I guess that’s why I like the combination of MD and MT so much: they fit this model perfectly!

Keep up the great work!
Audios
@Audios one way that I can go is that if you touch the same button in a button group twice, we go back to the last selected button. Thoughts?

Love Bomes, by the way! We have a Bomes-like app too, but it's way more/less powerful http://midiDR.com/mjdj
By going back to the last selected button, I assume you mean that it will be like pressing the button for the first time so it will be highlighted and will resend whatever MIDI message it's programmed to produce. That's pretty good; as I said previously, I'd prefer it not resend its message (so it doesn't reset anything) but at least it would remain highlighted.
You've checked out Bounce Back, I hope? http://midiDR.com/bounceback

1 Answer

0 votes
 
Best answer

This was implemented months ago. Check out the videos about Bounce Back here.

answered May 2, 2014 by MIDI Designer Team (Dan)
selected May 6, 2014 by MIDI Designer Team (Dan)
...