View Single Post
Old 09-19-2023, 09:24 AM   #4
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 7,759
Karma: 5446592
Join Date: Nov 2009
Device: many
Can't. As the watcher javascript to detect dom changes does not always work. Therefore File changed status is literally determined at close/leave points by comparing pre and post xhtml dumps from the QWebEngineView. It is the only way to accurately detect if changes have been made internally.

And remember PageEdit, as its name suggests, is a single xhtml page editor, not an epub editor. It work on a single file as a time and either saves the changes or does not when you leave that page in any manner.

But adding a "continue editing/don't leave" option is doable for a future release but you will not then be able to navigate away.

Last edited by KevinH; 09-19-2023 at 10:00 AM.
KevinH is offline   Reply With Quote