View Single Post
Old 07-28-2014, 03:35 PM   #1
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,657
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Editor plugin question

Is it possible for an editor plugin to leave an ebook in an unchanged (not needing to be saved) state?

At first I thought it might be :
Code:
self.boss.commit_all_editors_to_container()
or
Code:
self.boss.add_savepoint()
that was leaving the ebook in a "dirty" state, but commenting them out made no difference. Right now, I can open a book; run a plugin that checks a few things and makes no changes to the container itself; immediately close the book, and I'll be prompted about unsaved changes.

"self.boss.show_current_diff()" even shows no changes (between current, the checkpoint my plugin creates, and the "Start of editing session" ) and I'm still prompted to save the book when closing.

If it's not possible for an editor plugin to leave an ebook in a "clean" state, just let me know so I can stop trying to figure out what--in my plugin--is dirtying" it up!
DiapDealer is online now   Reply With Quote