Bug 148805

Summary: Image editor window larger than 2250px breaks image canvas space
Product: [Applications] digikam Reporter: Eric Stevens <mightye>
Component: ImageEditor-CanvasAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, mightye+kdebugs
Priority: NOR    
Version: 0.9.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 7.6.0
Sentry Crash Report:

Description Eric Stevens 2007-08-13 23:27:31 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

When sizing the Image Editor window greater than 2248 pixels wide, the horizontal canvas space available for the image shrinks substantially.  The resize handle for the side pane is half way between the side pane and the image canvas space.  Resizing the side pane will correct the right side of the image canvas, but the left side will remain about 25% of the window width away from the left side of the window.

Here are images demonstrating the problem:
Good (2250px wide): http://boole.mightye.org/temp/snapshot1.png
Bad (larger than 2250px wide): http://boole.mightye.org/temp/snapshot2.png

As a result I am unable to maximize the image editor window on my 30" screen.
Comment 1 Andi Clemens 2008-08-15 22:13:57 UTC
I can not confirm this.

Eric,
is it still valid? Otherwise I will close it.

Andi
Comment 2 Eric Stevens 2008-08-15 22:26:03 UTC
Yes, it seems to be, maximizing digiKam editor window (not main image viewer window) at 2560x1600 resolution, then collapsing the side panel so the image space takes up the full screen width causes the image to become thumbnail sized as in the sample images originally attached.

Digikam 0.9.3 using KDE 3.5.9 (Ubuntu Hardy Heron 8.10)
Comment 3 Andi Clemens 2008-08-15 22:35:33 UTC
I can not maximize the window to that size, only scale it manually to your dimensions or higher. But than I can not confirm it, maybe it must really be in maximized mode?
Have you tried digiKam 0.9.4 already? Maybe it was fixed in there?
Comment 4 Eric Stevens 2008-08-15 22:44:45 UTC
Sorry, I don't have access to 0.9.4.  

It happens whether the window is in maximized state or manually resized.  The images I'm using are 4320x2868, but even if I use 2560x1699 or 1024x768 files I see the same behavior.

File type doesn't seem to matter either - JPG and NEF [raw] show the same behavior).

The only thing that seems to matter is once the image canvas exceeds that threshold.
Comment 5 caulier.gilles 2008-08-16 08:04:49 UTC
Eric, 

Perhaps it's a side effect of :

-Open GL mode with windows manager. (do you use it ?)
-The KDE windows style (Which one is used ?)

Note: here is have 3 flat pannels to work in xinerama. I cannot reproduce this problem.

Gilles Caulier
Comment 6 Eric Stevens 2008-08-16 12:27:18 UTC
Actually Gilles you made me think it's related to the window manager.  I'm using Metacity under Gnome.  The issue appears with and without GL desktop effects.

When I first reported the bug last year it happened under both KDE and Gnome (the screenshots under my original report were from KDE), but now it seems to only happen under Gnome.
Comment 7 caulier.gilles 2008-08-19 10:58:59 UTC
Ah,

So it's a window manager style problem. Under Gnome, try to use another one...

Note : i never use Gnome, only KDE. This is why i never see this problem here.

Gilles
Comment 8 MightyE 2008-08-24 15:36:54 UTC
I see the same behavior using any of the built-in themes under Metacity (Ubuntu 8.10), and also using Compiz (Emerald window manager) on various window decorator themes.  The common aspect seems to be Gnome now.

Sorry for the delay, just back from a trip.
Comment 9 caulier.gilles 2008-12-06 08:10:00 UTC
Eric,

What's new about this report ? it still valid using digiKam 0.9.4 (using KDE3) or digiKam 0.10.0 (using KDE4) ?

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

*** This bug has been marked as a duplicate of bug 197483 ***
Comment 11 caulier.gilles 2022-01-29 06:08:45 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=197483