|
There is an issue entered on the Sigil website requesting an optional autosave feature so it has not been forgotten. It will require changes to the underlying code and it could have a performance impact, and as mentioned there are issues around saving corrupted files and mid-changes. So its not a simple thing to implement, but it will remain on the list to look at at some point.
In the meantime, you should definitely be saving your file every so often - certainly more frequently than every several hours - and particularly before major find/replace changes. This is true for Sigil, and pretty much any other software that is used. That doesn't help with the frustration of losing data from a crash that shouldn't happen in the first place, but might help when it happens again.
There is some confusion over what you are expecting to be saved. Once you have imported your HTML file into Sigil, you are working with an EPUB file that happens to contain html/xhtml/css/images/etc files. When you Save or Save As, you are saving the whole EPUB including all the documents inside the EPUB whether they are html or css, etc. There is no option to save/export individual files (at least at the moment as far as I know).
If you try to run Save or Save As and Sigil says there is a problem saving - then this is IMPORTANT. As was said above, Sigil is telling you something is wrong with a document in your EPUB (or where you want to save the file) and you need to correct this. This is why its important to manually save often - it is very easy to corrupt an EPUB file and Sigil won't save a corrupted file so the sooner you find out about the problem the better. The warning usually gives a you a reason for the issue, and you can run validation checks on the document to help.
You can always post any questions about using Sigil to this forum, and if you have specific bug or feature requests post them to the issue log after checking for existing issues.
|