https://bugs.kde.org/show_bug.cgi?id=364012
--- Comment #3 from Wegwerf <wegwerf-1-...@gmx.de> --- Probably some project token, sich as a hash, but can be even simpler, would suffice. It gets updated with each project edit after a save. The cache, in turn, remembers the most recent project token it had been used with. 1. user edits project, prerenders project, then saves project, then reloads: will pick up the cache contents as reloaded project token equals cached project token. 2. user edits project, saves project, prerenders project, the reloads: same as 1, project token equals cached project token. 3. user edits projects, prerenders project, then aborts and reloads project: cached project token doesn't match saved project token anymore, cache needs to be invalidated completely. -- You are receiving this mail because: You are watching all bug changes.
