PageEdit does not cache pages, but instead loads them directly to and from disk. So if you make changes in Sigil and use a tool that saves the changes to disk (ie. run any plugin or run a report, etc) those changes should be available the next time you navigate to that page in PageEdit but that was not its intent.
Again, PageEdit is NOT BookView. It is designed for simple edits and proofing of nearly final versions. It was NOT designed for going back and forth to make a change in PageEdit then a change in Sigil and then a change in PageEdit , etc. It assumes you want to work in a Visual environment. If you need to see the code itself, use PageEdit's Inspector to show the code of that Page, and using right click in the Inspector, you can even modify it at the code level if that is what you want. Otherwise simply save out of PageEdit, make whatever major changes you want in Sigil and relaunch it.
So exactly what are you trying to do that requires going back and forth repeatedly from Sigil to PageEdit to Sigil to PageEdit that can not be accomplished with the Inspector right in PageEdit?
Last edited by KevinH; 01-01-2020 at 10:21 AM.
|