Summary: | Tags set in Comments/Tags end up on the wrong picture | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Roger Larsson <roger.larsson> |
Component: | Tags-Captions | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 0.9.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.9.1 | |
Sentry Crash Report: |
Description
Roger Larsson
2006-09-03 18:58:18 UTC
This is depand how you have done the selection of images (using CTRL | SHIFT + mouse button or using only the mouse), because the Comments & tags side bar cannot process a selection of images but only work on the first selected image from the selection. Gilles Caulier No, there is only one way since you can only view one picture at the time in Image Editor! (you removed a vital part of the bug report). Roger, i don't understand exactly what you mean. Is you bug report can be only reproduce using Image editor ? Because the Comments & tags C++ Object is the same in Album GUI and IE, it's not clear for me... Gilles When I am in image editor I expect the image I show to be the one that becomes modified when I change a tag (select checkbutton to the right of the image, still in Image Editor). If Comments & tags is the same then it the Image Editor has does something wrong when it connects the entered data with the image. I think the tag modifications is not done until you move from the current image. Today I can not reproduce it - strange (new and fresh start of digikam) will see if something happens after awhile... Noted that changing a tag in Image Editor end then closing the image causes the tag to be lost... - another bug report or? I think the tag modifications is not done until you move from the current image. ==> yes. Noted that changing a tag in Image Editor end then closing the image causes the tag to be lost... - another bug report or? Not sure. Marcel have fixed a similar problem this week end (reported by me (:=))). To be sure, check out a fresh copy of current implementation from svn and try again. Gilles Roger, Can you reproduce the problem using 0.9.0 final release ? Gilles I have not seen this bug recently. |