FR - Efficient Way to See/Control Bypass State of an MXXX or MSF Module

[dmbaer]

Vojtech informed me (in an off-forum email discussion) that I should be using bypass rather than enable/disable to “turn off” modules not being used in an MSF preset. I don’t want to waste resources by keeping a reverb module working if the user isn’t using it, for example.

OK, that’s easily done, but using enabled/disabled rather than bypass is much less error prone courtesy of the visual feedback. You can double click on a module and its enabled/disabled state changes as does the color. If an MP changes the enabled/disabled state, you see this happen clearly just by looking at the grid.

But to discover if a module is bypassed, you need to click on it to see the state of the Bypass button in the module editor. If an MP changes the state, it’s not nearly as obvious as if the enabled/disabled state changes. And to toggle the bypass state, you need to have the module selected as well.

I’d like to propose the following as a workflow improvement.
1. Find some small visual device to indicate the bypass state of a module. The “circuit” lines connecting modules might provide a clue, but these are sometimes hard to decipher if modules are crowded together.
2. Allow something like ctrl + double-click on a module box to toggle the bypass state directly.

EDIT: OK, never mind about part 1. I was trying to make the transition from using Enable/Disable to Bypass and simply was misreading the signs. The visuals work just fine ... my error. However, part 2 would still be useful I believe.

[MeldaProduction]

Some different coloration for bypassed stuff should be possible. Not sure about ctrl+dblclick, usually nobody find about these, but I'll check.