-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
Persisting UI state between program invocations #140
Comments
I would like to work on it. Can you please see to this. |
My main instinct would be to use the existing QSettings (wrapped as RipesSettings) infrastructure to persist UI states (e.g. https://github.com/search?q=repo%3Amortbopet%2FRipes+ripessettings%3A%3A&type=code). |
I have worked on Kaidan which is explicitly a Qt-based project, in that we have QSettings implemented, and it persistently stores many states. We also have |
Currently, things such as the program loaded into the editor and the active processor are stored as settings and persisted between program invocations.
We should be able to add more features like this, to persist things such as:
The text was updated successfully, but these errors were encountered: