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.

Sign up for GitHub

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

Jump to bottom

Improve unsaved definition situation #9

Closed

thelabcat opened this issue Apr 27, 2024 · 0 comments

Labels

Owner

thelabcat commented Apr 27, 2024

Currently, if a definition is unsaved, there is no indication for that. The user must click the load button manually.

Possible solutions:

Make the definition constantly save. Eliminates the definition reset button.
Have the definition save and reset buttons be disabled unless the new definition does not match the old one. Add a method that is called on any write event to the text box which checks for this. Perhaps add an entire special_disable() method that handles all unique widget disabling after a global GUI re-enable has been done?

thelabcat added the enhancement label

thelabcat changed the title ~~Improved unsaved definition situation~~ Improve unsaved definition situation

thelabcat added a commit that referenced this issue


          Completed #9

74aa79d

thelabcat closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment