Replies: 4 comments
-
|
This is something on my wishlist also... being able to map switches to a purpose, and thus this can be changed in one central place, or even allow for easier moving of models from handset to handset, since you could basically say SC is my MODE switch on X handset, and SA is MODE switch on Y handset. We'll get there one day. Some people use Lua scripts to auto-create entire model profiles (which means you can basically have some variables at the top that define your switches, and thus easily make model wide changes. I seem to think I've seen a Lua tool that would let you move switches around, but I can't place a finger on it now... Or I'm confusing it with this Lua tool (which lets you transfer things like curves, LS, etc between models) |
Beta Was this translation helpful? Give feedback.
-
|
Another possible way to do it, is to edit the modelxx.yml file and do a search and replace for the switch name. This is a little risky, but I think it will work...I plan to try it and will post back. |
Beta Was this translation helpful? Give feedback.
-
|
This would be amazing as well, even as a Surface user |
Beta Was this translation helpful? Give feedback.
-
|
Good News! I was able to change switch names by editing the model.yml. It was pretty easy, but you do have to do it in 3 steps:
Although this is a reasonable workaround (for those comfortable editing files), I still think adding a Logical Name for a switch would be a very useful function. Is there a place where features can be requested and people vote to indicate popularity which would allow developers to determine priority? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is best illustrated by an example:
I'm using a 3-pos switch (SG) to select 3 modes on my model. I later decided that I would prefer to use another switch (SE) to set the mode.
This is now a hassle to change, as I need to find every instance of SG and change to SE. This likely means changes to MIXER and Special Functions, and Logic switch definitions.
This would be much simpler if I could define a logical name (eg. MODE) for the switch, and define MODE = SG
I would then use MODE in all the definitions for MIXER, Special Function, and Logic Switches
If I want to later change to switch SE, I simply redefine MODE = SE.
I thought I had a solution using the INPUTS screen, as I can define an Input called MODE and assign it to a switch, but the INPUTS can only be used in the MIXER. INPUTS cannot be used in Special Functions or Logical Switches.
I'm fairly new to EdgeTx, so I'm still learning a lot. Does anybody know a way to do this?
If not, can I make this a feature request?
Thanks,
Andrew
Beta Was this translation helpful? Give feedback.
All reactions