Yes, closing Sigil underneath PageEdit would be a huge no-no. Sigil is supplying the unpacked epub (that Sigil unpacks to its own temp files) to another app which will be erased when you close Sigil. So you effectively gave paths to files to PageEdit that no longer exist. Try deleting all the xhtml files out from under any e-reader while actively reading and it will have similar issues
If you do not need or want Sigil open, then unzip a copy of the epub you want to work on to someplace and then open its OPF file in PageEdit directly.
This might be a good use for Sigil's FolderIn and FolderOut plugins. If you have a book in Sigil, you can use FolderOut to save it someplace. You can safely close Sigil. Fire up PageEdit and do your thing. Then when you leave PageEdit, you can use Sigil's FolderIn plugin to get all your changes.
Otherwise, no closing Sigil behind PageEdit's back. You can of course minify Sigil at any point, just not close it as it will delete its files to clean up after itself.
Quote:
Originally Posted by un_pogaz
The new navigation and reading is so much easier than in pure Sigil. 
A window/panels for view and use the TOC would be a good addition, but this is very secondary.
BTW, Bug report: If you open PageEdit in ereader mode (content.opf), close sigil (but not PageEdit) and then try to navigate to a new XHTML page => PageEdit freeze and crash. |