Editor plugin question

[DiapDealer]

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 :

self.boss.commit_all_editors_to_container()

or

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!

[davidfor]

Yes, I hit that yesterday while playing with my Sort CSS plugin. I was simply writing lots of stuff to the console to get a better idea of what was in the files and not making changes, but I was still prompted to save changes when I exited.

OK, I just looked through my code and commented out all the things I thought it could be. Still had the update needed. But, the first pass I missed one. After the display of the differences I have

self.boss.apply_container_update_to_gui()

That seems to be the trigger. Even if I don't actually make any changes, executing that line will mark the file as dirty and need a save. That's probably reasonable.

[DiapDealer]

Originally Posted by davidfor

self.boss.apply_container_update_to_gui()

That seems to be the trigger. Even if I don't actually make any changes, executing that line will mark the file as dirty and need a save. That's probably reasonable.

Ah ... thanks for that! I can just create my own clean/dirty flag and then apply_container_update_to_gui() only when it's actually necessary.

Thanks again.