| Summary: | USB Storage size (and Local disk) are wrong | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Blindauer Emmanuel <bugs.kde.org> |
| Component: | Import-UMS | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mailinglist, opensourcecat |
| Priority: | NOR | ||
| Version: | 0.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Wrong disk size listed
first wrong value second wrong value image with the vrong values |
||
|
Description
Blindauer Emmanuel
2008-11-23 20:25:58 UTC
If i'm not too wrong, MArcel has fixed this problem this week end. Please chaeck with current implementation from svn (beta6) Gilles Caulier Created attachment 28969 [details]
Wrong disk size listed
Brendan, If i'm not too wrong, Marcel has fixed this problem with 0.10.0-beta6. Can you try again with recent code ? Gilles Caulier I'm using digikam-0.10.0-1.beta6.3mdv2009.1 and the bug is not fully corrected. The displayed size of USB Storage is ok now, but when importing photos, in the status bar of the opened window. I'm using digikam-0.10.0-1.beta6.3mdv2009.1 and the bug is not fully corrected. The displayed size of USB Storage is ok now, but when importing photos, in the status bar of the opened window there are still wrong values. Created attachment 28973 [details]
first wrong value
Created attachment 28974 [details]
second wrong value
Gilles, code I was using was current to the hour. Gilles, looking at the code it seems all these values and the textual representation come directly from KDiskFreeSpace and KIO conversion methods. Nothing we did wrong here? Created attachment 29149 [details]
image with the vrong values
The same problem persist with revision 894457 (08/12/2008). I'v also created an attachement wit a screenshot. Also confirming with yesterday code. To Marcel #9, Definitively yes... We use KDiskFreeSpace to scan media information. Values are returned by this method : http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/classKDiskFreeSpace.html#a600e0b7c5a3c5dfe8af4f3f8df94e9d Which return sizes in KibiByte (http://en.wikipedia.org/wiki/Kibibyte) After, value are displayed using KIO::convertSizeFromKiB : http://api.kde.org/4.x-api/kdelibs-apidocs/kio/html/namespaceKIO.html#5f45b12d68e8c5c62646ed6f239909c8 So, I don't understand where is the problem. Sound like a KDE API problem ? Gilles To all, Which KDE version you use ? Here using KDE 4.1.2, i cannot reproduce the dysfunction. Gilles Qt: 4.4.3 KDE: 4.1.82 (KDE 4.1.82 (KDE 4.2 >= 20081204)) "release 3.1" kde4-config: 1.0 digiKam 0.10.0-beta7 (svn of the 08 December) SVN commit 897807 by cgilles: api between KDE 4.1 and KDE 4.2 is slitly different and media size unit returned by KDE api have been changed from KBytes to Bytes BUG: 175925 M +4 -1 freespacewidget.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=897807 |