Bug 171310

Redirecting the digikam-0.9.4 for KDE3 to $HOME/Pictures the preview works fine.

René. 

There is a side effect somewhere. To solve this problem, go to tags view and go back to album view. thumbs appears ?

Look also in the console if some error messages are visible.

At end, try to use current code from svn (beta4) where Marcel has fixed a lots of code relevent of Digikam::AlbumManager core component.

Gilles Caulier

Hi Gilles,

After starting digikam without doing anything:
---
Found dcraw version: 8.87
File '' is not readable.
---

Switching between the tags view and the album view doesn't have influence on this. Nothing happens on console during doing so.

On "Tag" -> "New" I get a popup with
Create new tag in "/".
On the console I get another
---
File '' is not readable.
---
but only once, not more times.

Tell me if I can provide you more information.

René

Oh sorry, you are right.
I tried only the "Caption/Tags" on the right side.
Checking the real "Tags" view and returning to the album view the preview is shown.
Sorry, I'm still not fit with the new Digikam features ;-)

René,

This is a bug of course (:=)))

Marcel,

As you see this dysfunction from AlbumManager ?

Gilles

I can confirm this, too. Neither a imported folder nor freshly detected image albums (by scan for new images) do appear in the album view. Of course I'm using latest trunk.
The same for is true when adding new album collections.
By the way: What is the purpose of giving names to the collections? They will be renamed anyway. Or am I misunderstanding this.

Just wanted to mention that a restart of digiKam will display those new albums...

SVN commit 862616 by mwiesweg:

Restore these lines. I copied them and then inadvertently deleted them.

BUG:171310


 M  +2 -0      albummanager.cpp  


--- trunk/extragear/graphics/digikam/digikam/albummanager.cpp #862615:862616
@@ -2086,6 +2086,8 @@
     {
         case AlbumChangeset::Added:
         case AlbumChangeset::Deleted:
+            if (!d->scanPAlbumsTimer->isActive())
+                d->scanPAlbumsTimer->start();
             break;
         case AlbumChangeset::Renamed:
         case AlbumChangeset::PropertiesChanged:

Hmm for me this still isn't fixed...

Marcel,

is it really working for you now? I just tried it again in a pure KDE4 desktop as well as in a KDE3 environment, freshly imported albums and images don't appear.
I need to restart digiKam to see them.

Andi

Ok, I did fix a bug, but apparently not this one.
I can currently crash digikam by using Import->Add Images, and Image->Add Folders is not working for me. These are bugs of course.
What works is just copying over a folder from the command line outside digikam. This works well for me, the album and the contained picture appears when scanned. Does this work for you?

"Add Images" or "add folders" works fine here, also copying on commandline will show the images. The only thing that is not working is adding a new collection, if I do so I need to restart digikam.

Oh just found out that the new images are only visible if I copy or import them into an existing album, if I create a new one, the folder is visible but empty, just like if I had created a new collection.

I think I found the cause for the collection problem, a really tricky one, took a bit longer to find out: When a new collection is added, we start a complete scan, which uses a transaction; during the transaction, the changes I assume cannot yet be read from the db file, so the album is not available when the creation message comes to AlbumManager. I'll think about fixing that.

The other problem you mention in #13: How do you create the folder, from within digikam with New Album, from outside? How do you put images in there, from inside or from outside?

I created the album from outside, by commandline this time, need to check if it behaves the same when creating an album inside of digikam.

Marcel, CCBUG macro is not yet restored...

I CC your commit...

Gilles

SVN commit 864582 by mwiesweg:

When in a transaction, send out changesets only after completion of the
transaction, as other db connections will not be able to read the changes
so far.
Fixes the Collection-albums-empty problem for me.

CCBUG: 171310

SVN commit 864774 by mwiesweg:

Among some minor changes, fix one more stupid mistake:
Exclude the just added image from searching for identical files,
as obviously it will be falsely found otherwise, resulting in empty db entries.


 M  +14 -7     imagescanner.cpp  

Hi Marcel,

it seems to be fixed for me here, too. I'll close it again...

Thanks for testing Andi. I did find some bugs now but didnt do extensive testing myself. If anyone finds further problems in this area, please report again.