consider saving application state not only on application exit
Closed this issue · 1 comments
Deleted user commented
Currently it seems that the application state is only saved when the application (cleanly) exists. Here are various scenarios where the application doesn't get cleanly closed, perhaps there are more:
- application crash;
- windows kills the application on shutdown/reboot because it doesn't respond fast enough to the "exit" signal;
- windows crash / spontaneous reboot
These are not necessarily the fault of the eduVPN app, there's a lot of subtly and less subtly broken Windows installations out there, but perhaps something (more) can be done to "keep state" in case these happen...
rozmansi commented
Mind, that only settings that still do not trigger saving on the go are the window position and state (minimized, closed, etc.). Those settings are transferred from Windows to our settings collection on client close (or session end) and not on each client window move or resize. For performance reasons.