|
You can always press the save button of course. Why does everything has to have an autosave? Remember those old Sierra Adventures? The pesky 'Remember, save early, save often!' after you just died.
Crashes are hard to avoid sometimes and even harder to debug. Don't forget, it is the work of very few people with limited resources. They do this in their free time. Handling these kind of files with big chunks of text and S&R is complex.
Also, some things are out of their control. In order to have it cross-platform (think about it, that is quite unusual), some generic libraries and environment have to be used. There aren't that many cross-platform development environments available. The QT-framework is one of the few that is actually workable.
That does result in that all bugs in the framework are present. There are some serious issues with the rendering engine with regards to fonts and certain layouts. That is unavoidable and outside of their control to fix.
Font handling is not complex, but a very precise job. You really have to take care that you do it correct. That is not Sigil's fault, that is up to you to do correctly.
Nobody forces you to use it. At the moment it is the best software for the job. All the new features are actually requested by the users. Am I annoyed when it crashes? Sure I am. However, I usually can predict when it happens. When I do a big cut/past or complex S&R I always save beforehand. It is only a mouse-click away...
|