Bug 169213

Summary: Digikam should not enter new album after creating it
Product: [Applications] digikam Reporter: Eike Welk <eike.welk>
Component: Albums-MainViewAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: step247
Priority: NOR    
Version: 0.9.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 1.0.0
Sentry Crash Report:

Description Eike Welk 2008-08-16 02:26:52 UTC 
Version:           0.9.3 (using 3.5.9 "release 49.1" , openSUSE 11.0)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.25.11-0.1-default

When you create a new album, Digikam will enter this new album. However there is nothing to see in the new album, because the new album is by definition empty. 

Therefore I propose that Digikam should not enter new albums after it has created them. Instead it should remain in the album where it was, when the creation of the new album was requested.

This new behavior would be quite helpful for my workflow: I create new albums when an album contains very many images. After creating the new album, I drag some photos into the new album. 
The current behavior is a little disruptive for this kind of workflow: After creating the new album, I have to locate the (source) album, where the many images are, for a second time. I also have to locate the images for a second time and most likely I have to scroll until I find the images because there are many images in the source album. Only then I can drag the images to their new location. This lengthy procedure can be a little frustrating if you want to split a big album into multiple smaller ones.
Comment 1 step247 2009-05-27 12:41:29 UTC 
Eike Welk you are correct, this is a PITA when you work (sort, reorganize etc)  albums.
Comment 2 Andi Clemens 2009-05-28 08:56:06 UTC 
There is a new function to create a new album or move the selected images to an album in the context menu. This action can be used in your workflow.
If you select more then one image, the action will appear on top of the context menu.
Anyway I guess that it is still not very useful to switch to the newly created, empty album. I guess we should disable it.

Gilles, Marcel and others,
what do you think?

Andi
Comment 3 caulier.gilles 2009-05-28 09:06:27 UTC 
Agree. 

Dolphin, gwenview and konqueror do not have this behavior...

Gilles
Comment 4 Andi Clemens 2009-05-28 09:07:15 UTC 
One more note:

Some people create a new album by right-clicking on the parent and then select "New Album" from there. But if you right-click an album, it becomes selected.
This is why the "Create new album from Selection" action was introduces.
When pressing CTRL+N for a new album, it will always be a subalbum of the currently selected.
The "Create new album from Selection" fixes that, too. You can create the album anywhere you want, without losing the selection. Or you just move the images into an already existing one.

Eike, Step,
maybe this is what you are looking for?

Eike,
I just realized you are using a very old digiKam version, in which this action is not present.
It was introduced in digiKam 0.10 for KDE4. digiKam 0.9.3 is very old, latest and maybe last version of digiKam for KDE3 is 0.9.5.

Andi
Comment 5 Andi Clemens 2009-05-28 09:26:08 UTC 
SVN commit 973904 by aclemens:

When a new album is created, don't enter it immediately.

BUG:169213

 M  +0 -1      albumfolderview.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=973904
Comment 6 Andi Clemens 2009-05-28 09:29:07 UTC 
Gilles,

I don't have digiKam KDE3 anymore. If you plan to release 0.9.6, can you backport this one?

Andi
Comment 7 Andi Clemens 2009-05-28 09:31:27 UTC 
Hey, why is it unconfirmed again?
I just replied... hmm...
Comment 8 caulier.gilles 2009-05-28 09:49:02 UTC 
SVN commit 973914 by cgilles:

backport commit #973904 from trunk
CCBUGS: 169213


 M  +1 -2      albumfolderview.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=973914