Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No option or details on how to save changes #513

Open
bigjoncoop opened this issue Nov 15, 2024 · 2 comments
Open

No option or details on how to save changes #513

bigjoncoop opened this issue Nov 15, 2024 · 2 comments

Comments

@bigjoncoop
Copy link

Betaflight TX Lua Scripts: 1.7.0
Firmware: OpenTX - Latest Version
Hardware: Seems to be "at least" radios that have B&W non-touch displays. (e.g. Taranis QX7, X9D, X9)

Main Issue:
While in the Lua Script making changes, there is no Button/Selection or any details on how to save said changes... This makes the user automatically assume that the changes are auto saved, which of course there not. After trying multiple times and getting frustrated, users rightfully assume that the Lua script is broken.

This originally happened to me a while back and after trying multiple times and changes not being saved, I assumed that there was an issue with the Lua Script... Then months later after I stopped using it, I decided to factory reset my radio and start from scratch. To my surprise after setting everything back up and reinstalling the Lua script, the problem still persisted. Then after doing a Google search I learned that in order for changes to be saved you have to long press the "Enter button" and select "Save Page".

Over the past few years at meetups, I've had multiple people mention they were having the same exact issue. After showing them what the problem was they all basically said the same thing, why doesn't it have a save button in the Lua script or mention it in the Lua script menu, etc...

@klutvott123
Copy link
Member

@pfeerick
Copy link

I don't mean to add unhelpful "noise", but while that is true... it would be nice if the existence of the "long press" menu was somehow brought to a new users attention and/or the "unsaved" state of settings changes... The later is probably easier to indicate, but not sure how to make the former visible outside of a brief oneshot "first run" experience in the lua script that hints at the UI conventions and any "hidden" shortcuts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants