Quote:
Originally Posted by schwa
There are also messages to target LAST_TOUCHED_TRACK, LAST_TOUCHED_FX, LAST_TOUCHED_FX_PARAM, and FOCUSED_FX, but these do not change the device state. In other words, if the device has track 3 as the currently active track, and the user touches track 7 in the REAPER window, the device can send and receive messages targeting the last touched track (track 7), but messages targeting the currently active track will still target track 3.
|
We're now wondering if this is unnecessarily complicated. Perhaps instead of separate messages for LAST_TOUCHED_TRACK, LAST_TOUCHED_FX, FOCUSED_FX, there should just be config file settings like TRACK_FOLLOWS_LAST_TOUCHED, FX_FOLLOWS_LAST_TOUCHED, FX_FOLLOWS_FOCUS. If you enabled TRACK_FOLLOWS_LAST_TOUCHED, then touching a track in the REAPER UI would cause the device's currently active track to change.