Bug 225827

Summary: Image properties tabs inactive on default selected photo
Product: [Applications] digikam Reporter: Philippe ROUBACH <philippe.roubach>
Component: Geolocation-WorkflowAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, marcel.wiesweg, mike
Priority: NOR    
Version: 1.2.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 1.2.0
Attachments: gpswidget.png

Description Philippe ROUBACH 2010-02-07 12:51:50 UTC 
Version:           1.1.0 (using 4.3.98 (KDE 4.3.98 (KDE 4.4 RC3)), Mandriva Linux release 2010.1 (Cooker) for i586)
Compiler:          gcc
OS:                Linux (i686) release 2.6.33-desktop-0.rc6.6.3mnb

launch digikam

digikam opens ont he last used album

a photo is selected by default

you cans see :

gpswidget is in grey
photopreview is not displayed in the map

see the capture
Comment 1 Philippe ROUBACH 2010-02-07 12:52:32 UTC 
Created attachment 40583 [details]
gpswidget.png
Comment 2 Philippe ROUBACH 2010-02-07 12:53:22 UTC 
you must click on another photo to activate gpswidget
then
click on the first photo
Comment 3 Michael G. Hansen 2010-02-07 19:05:43 UTC 
I can reproduce it in trunk. But it seems to be a more general problem, as not only the GPS info tab, but all image information tabs (Properties, Metadata, Colors, etc) are grayed out.

Michael
Comment 4 Philippe ROUBACH 2010-02-07 19:54:51 UTC 
yes all is unactive
Comment 5 Marcel Wiesweg 2010-02-07 20:38:34 UTC 
I can confirm this. It's about 50-100% reproducable. Will have a look into this when time comes.
Comment 6 Marcel Wiesweg 2010-02-12 23:49:08 UTC 
SVN commit 1089347 by mwiesweg:

This signal is responsible for resetting the right side bar at startup.
It's a timer, so it was not reproducable everytime.

BUG: 225827

 M  +2 -1      NEWS  
 M  +0 -2      digikam/digikamview.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1089347
Comment 7 Michael G. Hansen 2010-04-11 19:01:14 UTC 
*** Bug 234078 has been marked as a duplicate of this bug. ***