Maybe a stupid idea, but I faced an issue with an on widgetValueChanged callback.
The solution was that in a specific variation the callback had to be somehow bypassed.
That brings me to an idea to „bypass“ a widget like it can be done with plugins.
When a widget is bypassed it would not react on changes via the mouse or scripting or assigned MIDI messages and therefore the on WidgetValueChanged callback would not be executed.
What do you think about?
Is there a reason your callback can’t query to see what variation it’s in so as to decide what to do?
No reason.
I just thought about a direct possibility to bypass a widgets action without going into scripting.
As I mentioned, maybe a stupid idea 
I never wanted to bypass a widget, but I already thought that we could add a “clickable” property. e.g. you don’t want a user to be able to click on a LED button because you use it for display purpose only, or in contrary you would like to be able to click on a text label or a shape widget to do something.