Persisting UI state between program invocations

[mortbopet]

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:

• Window sizes and states
• register display modes
• memory display modes
• ...

[tech-bash]

I would like to work on it. Can you please see to this.

[mortbopet]

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). However, i'd also really appreciate if someone would do a bit of research on and present how other Qt-based projects approach this issue, to guide our decision in how to implement this.

[tech-bash]

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 ripesettings , which we could integrate for our further use. The task could be a bit time taking too and me not being the best in Ripes would need assistance for sure to complete it :)