https://bugs.kde.org/show_bug.cgi?id=427481
Milian Wolff <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|NOR |LO --- Comment #1 from Milian Wolff <[email protected]> --- Hm, ideally we would somehow have a list of items for every project and then another step on top which de-duplicates that list. But I don't personally think this is a very critical issue, as one rarely opens projects in such a way. And if one does, then one wouldn't close the project again, or? So I'm setting the importance to LO. If this is important for your workflow, and you really need to have it fixed: Adding a vector of projects to every item will have a big performance impact if done naively. I would prefer not to do that. Rather, can't we check when a file is removed if there's another project that still contains it? Afaik that's a matter of iterating through the list of still-opened projects and doing a quick hash lookup each time. That will ensure that the performance impact of loading a project is minimal, and we also won't have to store more data in memory either. -- You are receiving this mail because: You are watching all bug changes.
