Bug 218819 - Implement albums tree-view colapse/expand history
Summary: Implement albums tree-view colapse/expand history
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Albums-TreeView (show other bugs)
Version: 1.0.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-15 18:48 UTC by DGardner
Modified: 2017-08-05 20:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.5.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DGardner 2009-12-15 18:48:32 UTC
Version:           1.0.0-rc1 (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

When I am tagging images, I view the thumbnails for the album and select
the tags from the "Captions/Tags" view on the right. I have about 400 tags
to choose from, so I like to work through all of the photos and set, say
the "Places/..." tags first, then the "People/..." tags, etc. This is easier
if I first expand the tag tree to expose the tags that I am likely to use
for the next pass before I apply them. To do this, I must first select an
image, as the whole tag tree is disabled until a selection is made.

The problem is that I often select a tag by accident when expanding and
collapsing parts of the tag tree and I have usually lost track of the
"random" image(s) I selected just to let me expand and collapse the tree
before I start.

It would be much easier if the tag tree was enabled all the time and if only
the check boxes were disabled when no image was selected. That way, I could
expand or collapse parts of the tree without selecting images and without
the risk of tagging those images by accident.
Comment 1 Jens 2017-03-02 13:02:04 UTC
I think this has been solved in the most recent Digikam version (5.4). Right?
Comment 2 caulier.gilles 2017-03-02 13:56:51 UTC
Jens,

Well nothing have be done on this feature, but for the Qt5 port perhaps a bug have been fixed.

If i remember, this feature exist since a long time. And i just tested : this work perfectly with 5.5.0.

Gilles Caulier