https://bugs.kde.org/show_bug.cgi?id=379511
Bug ID: 379511 Summary: Introduce additional sidecar types and fix bug in mime setup [patch] Product: digikam Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Created attachment 105344 --> https://bugs.kde.org/attachment.cgi?id=105344&action=edit Introduce additional sidecar types and fix bug in mime setup We already consider *.xmp files when renaming/moving/copying/... files, but some programs use custom extension for their metadata. To be honest, I only know of Rawtherapee's *.pp3 but that is reason enough. Therefore I introduced an additional field to the mime setup page for sidecar extensions. In contrast to the others, these files won't be registered in the database, but considered when doing IO operations. In the process I found an inconsistency that can lead to erroneous behaviour: In the GUI the user is told to use spaces to separate the extensions. The parsing function accepts either semicolons or spaces, but not both. The function that populates the input fields with existing extension inserts them with semicolons. So if you add a new extension ("ex1;ex2" -> "ex1;ex2 ex3") it won't be registered as a new extension but as a modification: "ex2" -> "ex2 ex3". As extensions can't (well shouldn't) contain spaces, I changed the parsing function to separate on both semicolons and spaces and adapted the explanation in the GUI. Also I changed to icons such that all mime icons are colored (not monochrome) according to the breeze-icons guidelines. As an aside: During renames this causes obviously failing thumbnail lookups for the sidecar files (was already the case for *.xmp). This is already addressed in my other patch about renaming. -- You are receiving this mail because: You are watching all bug changes.