Summary: | Folders thumbnails : custom folder icon overridden by default folder icon | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kio-extras | Reporter: | Mahendra Tallur <mahen> |
Component: | default | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | samrog131 |
Priority: | NOR | ||
Version: | 5.8.4 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Mahendra Tallur
2016-10-07 12:44:53 UTC
Hi ! Just updating after testing with latest KDE / Apps / Neon revisions. Bug still occurs. But I'm not sure I'm filing the bug at the right place. What component is actually responsible for displaying icons ? Thanks :) (In reply to Mahendra Tallur from comment #1) > Hi ! Just updating after testing with latest KDE / Apps / Neon revisions. > Bug still occurs. > > But I'm not sure I'm filing the bug at the right place. What component is > actually responsible for displaying icons ? > > Thanks :) By my knowledge the kio-extras. Folder thumbnailing is using the icon theme directory icon. ie: https://cgit.kde.org/kio-extras.git/ -> /kio-extras/thumbnail/thumbnail.cpp has, from line 466: //Use the current (custom) folder icon const QMimeDatabase db; const QString iconName = db.mimeTypeForName("inode/directory").iconName(); const QPixmap folder = QIcon::fromTheme(iconName).pixmap(qMin(m_width, m_height)); OK, I moved the bug and changed its name. Notifications are still being sent to Dolphin maintainers though, do I have something else to do ? Thanks a lot :) Hmm, it looks like it might be a one-line fix (not sure :-). If I could easily set up a development environment in a virtual machine. Any pointer ? If stumbled upon this : https://community.kde.org/Get_Involved/development but I'd need a tutorial indicating how to make changes to core components & test them, from the Neon Dev edition it would probably be even more relevant. Well, I'll look again ! I'm closing this and creating another report in the right area because I think something went wrong and the bug was not assigned to the right person :-) I hope you don't mind ! *** This bug has been marked as a duplicate of bug 375333 *** In the future, please do not do this. We can reassign bugs. Yes, sorry about this :( Actually I changed the "product" field but it didn't change the "referee" so the relevant persons didn't receive the notification (I guess ?). Was there another way to do this ? Thanks and sorry again for the inconvenience ! If you change either product or component, the checkbox "Reset Assignee to default" should automatically get checked. If not, you might need to click the "(edit)" link next to "Assignee", and check this option manually. But this time it is our fault, because we missed comments #3. @Christoph : thanks for your replies. I'm pretty sure there is no "edit" button next to "assignee", I am probably not allowed to do it as a regular user. Okey, I reported bug 375528 for this issue. Hopefully it reflects what was going on. |