Bug 281801 - Setting TAGs from the menu does not respect "auto tag" setting (set parent)
Summary: Setting TAGs from the menu does not respect "auto tag" setting (set parent)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Usability-Menus (show other bugs)
Version: 1.9.0
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-11 13:25 UTC by Nadav Kavalerchik
Modified: 2017-08-02 21:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 2.2.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nadav Kavalerchik 2011-09-11 13:25:49 UTC
Version:           1.9.0
OS:                Linux

When i right click an image to set a new tag (or several images) and then choose a TAG that has parent TAGs. only that TAG is set and not the parent TAGs, although it is set for "auto parent"

Using the TAG panel, it works just fine :-)

btw, should the "set auto tag" be in the "configure digikam" dialog?
( It took me some time to find it, maybe it is just me )

Reproducible: Didn't try

Steps to Reproduce:
When i right click an image to set a new tag (or several images) and then choose a TAG that has parent TAGs. only that TAG is set and not the parent TAGs, although it is set for "auto parent"

Actual Results:  
Only the current TAG is set.

Expected Results:  
Set the parent TAGs

OS: Linux (x86_64) release 2.6.38-11-generic
Compiler: cc
Comment 1 caulier.gilles 2011-09-11 13:33:55 UTC
Same here. Please check 2.1.0 version, just released. 1.9.0 is pretty old now...

Gilles Caulier
Comment 2 Marcel Wiesweg 2011-09-11 13:57:29 UTC
I think the auto-tags setting is indeed local and not a global setting
Comment 3 Nadav Kavalerchik 2011-09-11 14:16:39 UTC
I have used the instructions (for Kubuntu users) of moving from Digikam 1.9 main packages to 2.x ppa packages on the : http://www.mohamedmalik.com/?p=1019 blog, and upgraded my Digikam to version 2.1.0 and the issue is now solved.

Thanks :-)