EdgeTX
Add options to disable radio and model menu tabs. Include INPUTS, MIXES, OUTPUTS and DISPLAY
Is there an existing issue for this feature request?
- [x] I have searched the existing issues
Is your feature request related to a problem?
I really like the additions that where made to deactivate certain tabs.
It would be nice however to make it more complete, and allow also the INPUT, MIX, OUTPUT and DISPLAY tabs to be selectable for deactivation.
There are two use cases:
-
Block access to these screens for other people using your radio This is extremely useful in club situations with club radio's being used for training purposes. Students like to fiddle around, where this is not intended. There are workarounds to this by restoring backups etc., but just blocking these screens would already stop unintended changes by unexperienced users on an in between session level.
-
Support custom built model templates with custom scripts to configure them. Block access to the above screens and use TELEMETRY apps to allow only certain settings to be changed using custom menus in this telemetry app is an interesting setup. This would allow people to build custom models accompanied with scripts to manage them. It is quite easy to write a custom app to allow for only a few specific parameters to be changed. It would possibly motivate people to configure predefined models with setup 'wizards' for certain airplane types, and allow manufacturers to increase their commercial proposition by providing such templates with accompanying configuration apps. Since the screens are still possible to access after changing the settings, it will still allow users to adapt these templates and enhance using the full power of EdgeTX.
Describe the solution you'd like
Allow the INPUT, MIX, OUTPUT and DISPLAY tabs to be selectable for deactivation.
Describe alternatives you've considered
No response
Additional context
An alternative could be to make certain lines in every page 'locked' or even 'invisible' based on a general model setting called 'level', being 'new', 'daily' and 'expert'.
So for every level, lines could be made invisible, ineditable, or editable.
Different variations on how to achieve that goal.
The concept of user profiles or privileges makes sense, especially for the color screen interface, but until that is around I think hiding basic settings isn't a good idea. It doesn't even make sense unless you have privileged and non-privileged users. I do like hiding unused features but that's a different thing.
