Quote:
Originally Posted by MixMonkey
I think if you solve the Focus FX problems, this won't be an issue.
I saw it as a way of avoiding the FocusedFXNavigator for surfaces that didn't have displays, for people who had one MCU/XTouch type surface and another MIDIFighterTwister/BCR2000 type.
They could have the FX menu appear on the first surface, but have the selected FX map to the second.
From what I've seen so far, people using surfaces without displays for FX mapping tend to gravitate toward the FocusedFXNavigator, so if that is watertight, I don't think anyone would bother with the method I've just described.
|
Thanks, yeah, it's gone now, removing it resulted in a substantial complexity reduction.
I'm on a bit of a Dalek mission right now, looking for overly complex code that provides little benefit