View Single Post
Old 01-20-2018, 08:26 AM   #271
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,696
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Doitsu View Post
I've got a related question: is there a built-in property that I can use to make Sigil display the dirty-flag asterisk even when no file was changed? (I know that I can simply add and remove a dummy file, but I'm wondering if there's a more elegant method using a built-in property.)
Your method is really about as good as any, to be honest. There is no dedicated "dirty" property for the plugin framework that could be set by a user. The plugin wrapper simply has "modified", "added" and "deleted" dictionaries that are maintained so that PluginRunner knows what duties to perform whenever control is returned from the plugin to Sigil. Manually manipulating those dictionaries would be no more elegant than your suggested solution (perhaps even less so), and could potentially crash the launcher if handled incorrectly.
DiapDealer is offline   Reply With Quote