Bug 185764

Summary:	File dialog preview pane makes itself bigger
Product:	[Frameworks and Libraries] kio	Reporter:	Brendon Higgins <brendon>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra
Priority:	NOR
Version:	4.2.0
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	The first time I opened the file dialog. I cancelled that, and opened the file dialog a second time. Again, a third time. And a fourth. See where this is going?

Description Brendon Higgins 2009-02-28 01:59:37 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Sorry if I haven't assigned the right product, it's difficult to know. Packages from Debian experimental.

As the title says, when you open a KFileDialog it tends to have a wider side preview pane than before. I'll attach an example sequence. All I've done between each image in the sequence is to click cancel, then open the dialog again with File->Open.

The pane should keep a consistent size. Having to keep pulling it back is getting quite irritating.

I think it's something to do with the way it generates a first preview. In some situations it doesn't generate a preview immediately when the dialog comes up, and in those situations the pane doesn't seem to resize itself.

Peace,
Brendon

Comment 1 Brendon Higgins 2009-02-28 02:13:20 UTC

Created attachment 31692 [details]
The first time I opened the file dialog.

Comment 2 Brendon Higgins 2009-02-28 02:14:13 UTC

Created attachment 31693 [details]
I cancelled that, and opened the file dialog a second time.

Comment 3 Brendon Higgins 2009-02-28 02:14:59 UTC

Created attachment 31694 [details]
Again, a third time.

Comment 4 Brendon Higgins 2009-02-28 02:15:40 UTC

Created attachment 31695 [details]
And a fourth. See where this is going?

Comment 5 Dario Andres 2009-03-02 01:30:27 UTC

I have fixed this for KDE 4.2.1 and KDE4.3 :)
Thanks for reporting!

*** This bug has been marked as a duplicate of bug 160400 ***