Bug 69884

Summary:	statusbar forces minimum window-width
Product:	[Applications] gwenview	Reporter:	nutshell42
Component:	general	Assignee:	Gwenview Bugs <gwenview-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description nutshell42 2003-12-08 21:47:13 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources

The problem is that the minimum window-width of gwenview is dictate by the width of the statusbar contents. In the case of a long file-path (in this case multiple directories to a zip file and some more inside the zip) the gwenview window uses nearly one and a half screens (1280x1024 so it's rather big with 640x480 this should be even more common) and can't be made smaller because the statusbar insists on showing the whole path.

It's not a showstopper but it's rather annoying which is unfortunate because gwenview is the first kde image-viewer that could replace gqview =)

Comment 1 nutshell42 2003-12-08 21:51:12 UTC

Very nice, triple post - I actually submitted twice because I got a server error on the first try but I have no idea how it got send three times =/
Sorry

Comment 2 Thiago Macieira 2003-12-08 21:54:59 UTC

Closing duplicate.

Comment 3 Thiago Macieira 2003-12-08 21:55:55 UTC

Sorry, reopening one.

You closed the lowest and highest numbered entries...

Comment 4 Aurelien Gateau 2003-12-08 23:28:13 UTC

What version of Gwenview are you using? In version 1.0.0, the folder in the status bar should get squeezed if you reduce the window width.

Comment 5 nutshell42 2003-12-30 19:08:29 UTC

I'm sorry this reply took so long but I was confined to Windows for some weeks and I'd simply forgotten about this, sorry =)

I had a rather recent CVS build (mid-November or so) and actually had looked through your Changelog whether it was resolved (which according to the Changelog was in March iirc, my build was definitely newer than that).

That said, the bug vanished when I upgraded to 1.0 so who am I to complain ;)