https://bugs.kde.org/show_bug.cgi?id=454206
--- Comment #7 from Martin Kyral <sine.nom...@centrum.cz> --- (In reply to Martin Kyral from comment #6) > The config option seems perfectly fine to me. Let the user decide that's > best for them. > > The problem is, that KDCraw fucntionality is apparently broken (maybe by > kimageformats 5.99) for quite a while. So, the KDCraw code is still present > but broken. I tried myself with gwenview patched to prefer KDCraw. > > I am looking into the code trying to understand what happens with the data. What happened in kimageformats 5.99? Qt Raw pluging support was implemented. That broke kdcraw pipeline in gwenview, which has been 'fixed' by forcing gwenview to use the Qt RAw plugin as well, which works with the small caveat that it is by orders of magnitude slower, than what was before, rendering gwenview virtually unsable in some use cases (such as crawling through a folder with large number of raw files, which is very common situation everytime one comes home from a shoot). I suppose, kimageformats Qt Raw plugin code shall be reviewed and fixed so it doesn't break code in gwenview that does not utilize it. -- You are receiving this mail because: You are watching all bug changes.
