So I'm working on my own APC40 modes, and I've run into an irregularity that has me stumped.
I've got it set so that the four buttons above the transport controls are my mode selectors, and the first one puts the APC40 in "normal functionality" mode, with the exception that those four buttons remain as mode selectors.
When any mode besides "normal" mode is engaged, I've got all the default functionality disabled via enable_0 commands. This seems to work perfectly, with the exception of the pan, send_a, send_b and send_c buttons. While they appear to be disabled (they're not lighting up with presses, etc.), as soon as I re-engage "normal" mode, the APC40 recalls which one of these four was last pressed while disengaged, and returns to normal mode in that state.
For instance: I'm in normal, and the track control is set to pan. I jump into one of my other modes, and hit the send_a button while in that mode. When I jump back to normal mode, the track controls are set to send_a. Nothing else seems to function this way (i.e. if I press the button that mutes track 1 while in one of my custom modes, and jump back into normal mode, track 1 is not muted. This is what I want to happen here, too.)
I realize I could just do this manually (set up something to store the track control last set and bang it out when I jump back into normal functionality), but it's bugging me. Is there a command I can send the Track_Control component to stop it from updating while disabled?