I built Sigil with the
last commit and I see that it is OK.
It also handles other files that were causing a crash when calling the epub file directly (or double-clicking), such as those with errors in the container.xml or encryption.xml file.
I specifically corrupted the files and Sigil handles the exceptions very nicely. If only it is able to fix the file it does so, and if not it informs that something is wrong. It handles even if the container.xml file is completely missing.
I have a feeling that one of these cases could be solved (when an ncx file is missing, but there are entries in the opf file that identify this missing file), but I guess it's a waste of time for such a rare case.
Summary: However, creating a new file before the message is the solution. A little strange, but it works.
Thank you!
@DiapDealer: And as for the differences in Qt (I was worried about that too), I have the June 28 version from your repository, so I guess there are no differences here.
Edit: Oops. I was still supposed to test without the maximized Sigil window, but I immediately downloaded a fresh version from github and didn't check that.
But I did a test on another “faulty” files on released version 2.3.0 and indeed - when the main window is not maximized this crash problem does not occur.