Quote:
Originally Posted by mrprobert
Unless, the plugin has a method to find Sigil's process ID, it won't know if Sigil has quit and restarted.
I withdraw my request.
|
You still have not explained why that matters? Why is this a problem for a plugin cache?
1. Startup Sigil load epub A
2. Run your plugin which completes
3. Save epub A
4. Quit Sigil and restart it and load epub A
5. Run your plugin again.
How does Sigil restarting invalidate your plugin's cache as that cache must depend on the state of the files inside the epub it is run on. So a plugin derivable cache key is already possible with no changes based on file sha sums.
In other words, why do you need the Sigil process id? How does that help?