Version: 0.7 (using KDE KDE 3.3.2) Installed from: Unlisted Binary Package I'd like digikam to have the feature to View->Sort Images->By Comment Thanks for your consideration --Allen
My CC to you was rejected so c&p from my mail: The only usage of this feature would be faster finding interesting images with particular comment. Much more robust solution would be 'quick search' bar known (and loved) from JuK, KMail, etc.
> My CC to you was rejected so c&p from my mail: Hmmm... did you CC winterz@verizon.net or winter@kde.org? > The only usage of this feature would be faster finding interesting > images with particular comment. Much more robust solution would be 'quick > search' bar known (and loved) from JuK, KMail, etc. > Also helps to group images together with similar comments, which is why I want the feature. I agree that the 'quick search bar' would be great. -Allen
Dnia środa, 5 stycznia 2005 19:55, Allen Winter napisał: > > My CC to you was rejected so c&p from my mail: > > Hmmm... did you CC winterz verizon net or winter kde org? winter kde org. Maybe problem with wp pl. Probably due to spammers it is blocked from many domains :/ > Also helps to group images together with similar comments, which is why > I want the feature. I agree that the 'quick search bar' would be great. Another feature I miss in digiKam: real batch comments editor. Adding the same comments to many images, even output of script. I was planning something like this for cdigi but doesn't have time :(
I'm honestly not sure if it's a good way to sort pictures, a search(if not already existing) for certain comments would be better imho.
If you do you a quick search, also the comments fields (and tags) are searched for. For grouping images with similar comments, wouldn't it be much better to use tags? Ad #3 from Mikolaj: Now you can mark several images and change the comment simultaneously. Also this wish did not get that many votes. Allen, what do you think, do you still need this feature?
Yeah, you can close this bug if you want. I'm ok with the solutions you've implemented.
OK, thanks a lot for the feedback (even though it wasn't me who implemented anything for this ;-). Closing this bug as fixed.