Global "Logical Switches" ??

[Johanl1964]

Am I the only one who misses the possibility of having LS as global? For example, I use toggle as on/off on many functions that are the same for all model memories, so having to create a new "LS function" every time feels a bit strange considering that ETX is so adaptable!? But getting LS as global might be a "technical impossibility" ??

[raphaelcoeffic]

But getting LS as global might be a "technical impossibility" ?

The question here is: how do you want to use these global LS? How would they be addressed? LS are not doing something on their own, they are used as sources for something. That something is either a "Global Special Function", or anything in the model configuration. Having global SFs use global LS would be easy, the rest might introduce a bunch of conflicts with the existing LS in the model. Or we'd need to be able to address them separately. Now having the model depend on something that's defined at radio level may not be such a good idea, since they can easily get out-of-sync.

[Gernod]

Since the OP is specially refering to the case of using the Logical Switches and Special Functions to make a secure "Motor disable" switch, what about a Special Function which accomplishes that in one step? Older Versions of OpenTx had that back in the days if i remeber correctly.

[inventor7777]

Huge +1 on this. See my previous issue/feature request @ #5125

[thomaskistler]

+1. I have a "complicated" trainer setup where I can enable the trainer with a physical switch, but it automatically disables as soon as any of my inputs change. This requires 11 logical switches. This setup is the same for any of my planes and I currently have to painstakingly duplicate it with every model.

I also have another setup where I listen to single, double, and triple clicks on my momentary switch to encode timer reset and session reset. Again, multiple logical switches that have to be duplicated with every model.

[thomaskistler]

I’ve put together a draft specification for Global Logical Switches, building on the ideas discussed here.

It proposes 64 radio-wide logical switches (GL01–GL64), defined once in radio settings and usable in Global Functions and model settings, with radio and Companion editing.

This is a proposal only, not an implementation. I’d appreciate feedback on whether it covers your use cases and whether any behavior should work differently. I’ve also linked it from the feature request, #5125, to keep the proposal connected to implementation tracking.