[Zubersoft]

The only danger with this is it could potentially create an endless loop if the MIDI action sent a MIDI message which caused the device to respond with the same message that triggered the MIDI action. I will also have to make a number of changes to the UI for selecting the action for the MIDI action, as right now, you just pick an entry from the dialog, but there aren't additional settings you have to specify. If you are sending a MIDI message with the MIDI action, I then have to add a way to enter the one or more MIDI messages that will be sent in response to triggering the action. So it's not a super quick and easy change to make. I'll also have to dynamically insert a list component into the "New MIDI Action" dialog to specify which MIDI messages to send, and make sure that this is not confusing, as there is already a "MIDI Messages" label, so I would need to change it to show which is for sending and which is for receiving.

The MIDI action field in the database for tracking what action to trigger also doesn't have anywhere to store which MIDI messages to send (which requires an additional database table), so I'd have a lot of code I would need to add for updating the database, which also creates incompatibilities between versions.

Mike