Bug 215473 - Remember openend albums after closing digikam
Summary: Remember openend albums after closing digikam
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Albums-MainView (show other bugs)
Version: 1.0.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-20 20:24 UTC by Simon
Modified: 2012-06-27 11:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 1.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon 2009-11-20 20:24:07 UTC
Version:           1.0.0-rc (rev.: 1050601) (using 4.3.2 (KDE 4.3.2), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-6.slh.2-sidux-686

Since my last build from svn (maximally one week ago, where something with the Album handling has changed) digikam doesn't remember anymore which album I had opened in the Albums sidebar.
Comment 1 Simon 2009-11-28 08:59:42 UTC
bump ;)

Should this perhaps be in the final 1.0?
Comment 2 Marcel Wiesweg 2009-12-07 17:55:49 UTC
Not reproducible here, works nicely. Simon, anything special to bring it on?
Anyone else who can confirm?
Comment 3 Simon 2009-12-09 10:56:47 UTC
Sorry, couldn't re-compile digikam earlier.
Current SVN: Still the same problem. The Albums sidebar always shows collapsed directories:

My Albums
> Fotos

Although the pics shown in the Preview are
My Albums
> Fotos
> > Subdirectory
> > > Another subdir
> > > > Here.
Comment 4 Marcel Wiesweg 2009-12-09 18:25:12 UTC
Ok so it's about the expanded/collapsed state of the tree view?
Here, digikam precisely restores opened or collapsed tree, and restores the currently selected album as well.

In the digikamrc file it's stored like this:

[AlbumFolderView]
LastSelectedItem=155
OpenFolders=0,138,106,108,116,72,58,63,139,143,136,85,141

where the numbers are internal album ids.
Comment 5 Simon 2009-12-28 17:15:23 UTC
Exactly. 

But now it seems to be fixed in current SVN, working again here.
Comment 6 caulier.gilles 2009-12-28 18:06:28 UTC
Simon, this file can be closed ?

Gilles Caulier
Comment 7 Simon 2009-12-28 18:08:37 UTC
If the problem does not intend to appear again in a later version then yes ;)

Simon
Comment 8 caulier.gilles 2009-12-28 18:10:40 UTC
This is the goal, of course. Feel fre to re-open if necessary.

Gilles Caulier