Bug 197483

Summary:	High resolution screen window narrow width
Product:	[Applications] digikam	Reporter:	Con Kolivas <kde>
Component:	Usability-Ergonomy	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, mightye, tschenser
Priority:	NOR
Version:	0.9.4
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:	1.1.0
Sentry Crash Report:
Attachments:	Sample window 1 Sample window 2

Description Con Kolivas 2009-06-22 11:11:29 UTC

Version:           0.9.4 (using 3.5.10, Debian Package 4:3.5.10.dfsg.1-0lenny1 (lenny/sid))
Compiler:          Target: i486-linux-gnu
OS:                Linux (x86_64) release 2.6.30-ck1

Upon upgrading to a very high resolution display 2560x1600, I note that any windows that digikam launches itself (ie after the application has started) have very narrow frames that I cannot increase the width of. The application when launched itself has frames that are appropriately sized, but not any windows launched afterwards. I'll be attaching screnshots of the offending windows.

Comment 1 Con Kolivas 2009-06-22 11:13:20 UTC

Created attachment 34726 [details]
Sample window 1

This is the main window that opens when I launch digikam after "camera detect and download" thereby being a window that is launched after digikam has started.

Comment 2 caulier.gilles 2009-06-22 11:14:25 UTC

0.9.4 ==> try 0.9.5 or better 0.10.0

Gilles Caulier

Comment 3 Con Kolivas 2009-06-22 11:14:26 UTC

Created attachment 34727 [details]
Sample window 2

This is the window launched by the "edit" option.

Comment 4 Con Kolivas 2009-06-22 11:15:17 UTC

Oh that was a quick response! Sorry I'm just using what came with debian stable. We'll see what happens in the future when I get around to upgrading.

Comment 5 caulier.gilles 2009-06-22 11:16:07 UTC

Sound like a problem in Qt QSplitter size encoding. Must be fixed in Qt4 (digiKam 0.10.0)

Gilles Caulier

Comment 6 Con Kolivas 2009-06-22 11:24:57 UTC

Thanks. Should I change the status of this bug? I can't confirm it's fixed on newer qt/digikam myself at this time unfortunately.

Comment 7 Mikolaj Machowski 2009-06-22 19:45:30 UTC

This thing was reported before. I think it was closed (cannot find on list of opened bugs) but don't remember if it was due to actual fixing or lack of feedback from reporter.

Comment 8 caulier.gilles 2010-01-26 09:30:01 UTC

Con,

Can you try again with digiKam 1.0.0 release. Thanks in advance

Gilles Caulier

Comment 9 Con Kolivas 2010-01-28 10:00:35 UTC

Having upgraded to debian testing with kde 3.4.3 and digikam 1.0 I can confirm this is no longer a problem. I can't comment on other versions of kde.

Comment 10 caulier.gilles 2010-01-28 10:11:04 UTC

Thanks to report. I close this file now.

Gilles Caulier

Comment 11 Jens Mueller 2010-01-28 10:58:58 UTC

This looks like the same as https://bugs.kde.org/show_bug.cgi?id=148805, isn't it?

So this can be closed as well, Gilles?

Comment 12 caulier.gilles 2010-01-28 11:00:04 UTC

*** Bug 148805 has been marked as a duplicate of this bug. ***