Version: 0.1.0 (using KDE 4.2.90) Installed from: Ubuntu Packages I think digiKam really needs to hide geo tags (geo:lon, geo:lat and eventually similar formats) or even any "machine tag" (namespace:predicate=value) from the UI. I don't think it makes any sense to have hundreds or thousands of such tags in sidebars or context menus. For some notes about machine tags: http://www.flickr.com/groups/api/discuss/72157594497877875/ PS: I couldn't build the latest snapshots but it's my understanding that no recent commit has fixed this issue.
Sorry, i don't understand your problem exactly. Can you attach some screen-shots ? Gilles Caulier
Created attachment 34520 [details] Machine tags like geo:* can quickly make a tags tree/menu unusable. geo:*= are the most common form of machine tags because they are used by many geo tagging applications and for instance by flickr when a photo is uploaded. These tags will obviously make the digikam tags list become huge and fill the whole UI. Not sure if it would be best to hide only geo tags or any machine tag. Comments are welcome.
Created attachment 34521 [details] Tags context menu taking the whole screen because of geo:* tags
Fabrizio, This code is beta2. it will be released in one month, not before. I recommend to compile digiKam & co yourself. Gilles Caulier
Sorry, but no chance... Your image is tagged with dumy GPS info set as IPTC keywords... This is definitively a _wrong_ way. EXIF and XMP as dedicated tags for GPS info. digiKam has just used IPTC keywords to create new Tags in database. Your image have been managed by a wrong program. We will not make a wrapper only for this specific case. Gilles Caulier
The "wrong program" seems to be flickr, so you should really consider implementing "hidden" tags. There are also a lot of other wishes requiering a more complex tag system with hidden tags or database only (not written to image) tags, e.g. #129132 "Hidden tags for archiving purposes" #128333 "digikam automatic photographic tags" #181708 ""fast" tags, that are not written to database"
Just added another Wish that would solve this problem en passant. https://bugs.kde.org/show_bug.cgi?id=338048 but i see it's kind of a duplicate of the #'s you linked (hidden / fast tags)
*** Bug 287510 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 265880 ***
Fixed with https://bugs.kde.org/show_bug.cgi?id=265880