Menu
▾
▴
#160 Check for unsaved changes before Exit
I'm getting addicted to using Viking and organizing my tracks and I've got lots of editing to do. However, I've been burnt a few times by closing Viking before saving my changes. So it would be very much appreciated if this can be added to the next build. Even better if you can add a auto save mode. Thanks for all the hard work put into Viking already.
This has been a long standing issue - a duplicate of this:
https://sourceforge.net/p/viking/feature-requests/11/
However It's possible I may try a specific modification warning (rather than tie it in with an Undo system) as at least it would get done...
I estimate there's around at least 150 edit points (a simple count of 'emit_update' usage in the code) to cover and other instances to capture.
The emit_update calls are performed when anything is changed and could be an alternative avenue to investigate for where to put 'modified_this' markers.
Of course some update points are after startup / file loading / zooming / moving the viewport which are not modifications in the normal sense.
One tip - if I've left a window open for a length of time that I've probably been editing - is to check the File->Properties to see the date of the last time it was saved to see whether I need to save it or not before closing. But of course this is not ingrained behaviour and I still close it without thinking and then go D'Oh!.
Some time ago I did some preliminary work around some autosaving - inspired by Blender:
https://docs.blender.org/manual/en/latest/troubleshooting/recover.html
Which I might try to resurrect (and try to remember what issues led me to abandon it at the time).