https://bugs.kde.org/show_bug.cgi?id=363510
--- Comment #16 from Torsten Crass <torsten.cr...@ebiology.de> --- OK, I found out what's going on! After installing tons of dependencies, I compiled and debugged the digikam 4.4.14 source (from http://download.kde.org/stable/digikam/digikam-4.14.0.tar.bz2) from within kdevelop. The problem resides in the function QString DItemDelegate::squeezedTextCached(QPainter* const p, int width, const QString& text) const at line 184 in .../core/libs/widgets/itemviewditemdelegate.cpp. It seems that my problematic filenames prove that unlikely events like cache collisions are prone to occur sooner or later, regardless how unlikely they may seem. (Think Fukushima... ;) When commenting out lines 191-194, which return a cached version of the squeezed filename, if existant, the correct filename gets displayed in the album view, freshly generated by applying the squeezedText function to the filename. I suppose very little can be done about this. On the other hand, if you digikam developer folks can't reproduce my problem in 5.0, something must have changed in the sourc, preventing that cache collision from happening any longer. So I guess I'll for now stick with my modified digikam version with the uncommented caching code and just wait for 5.0 to eventually show up in Debian. Anyway, thanks for your great work on this great application! Cheers -- Torsten -- You are receiving this mail because: You are watching all bug changes.
