Bug 51571

Summary:	KMainWindow should save more than just the dimensions
Product:	[Unmaintained] kdelibs	Reporter:	Neil Stevens <neil>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist	CC:	esigra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Neil Stevens 2002-12-06 13:00:37 UTC

Version:           unknown (using KDE 3.1.1 (CVS >= 20021124))
Installed from:    compiled sources
Compiler:          gcc version 2.95.3 20010315 (release)
OS:          Linux (i686) release 2.4.19

Usually, but not always, when I open a new maximized Konqueror window (my Web Browsing profile has a maximized window), the window will appear two pixels below the top of the screen.  The maximize button shows that KWin thinks the window is maximized, but the window is just in the wrong position.

None of the maximized windows in my saved session ever do this, it's just new windows that get opened, and the only new maximized windows I ever open are Konqueror.  So whether this is specific to Konqueror's windows I'm not sure.

In case it matters, I'm using the B II plugin.

Comment 1 Neil Stevens 2002-12-06 13:49:57 UTC

This bug turned out to be a very weird interaction between KMainWindow and some 
smart KWin behavior. 
 
Konqueror's view profile uses KMainWindow::saveMainWindowSettings to save its 
window size.  My window was maximized, but KMainWindow took no notice of that, 
saving only the dimensions of the window.  Unfortunately, in my upgrade from KDE 
3.0 to KDE 3.1, two more pixels came available to my desktop (probably from kicker 
reserving less space).  So what was horizontally and vertically maximized in KDE 3.0 
was only horizontally maximized in KDE 3.1! 
 
If KMainWindow would save whether the window is maximized or not, then weird 
problems like this would never happen. 
 
thanks,

Comment 2 Stephan Kulow 2008-08-24 11:40:45 UTC

0 votes in 5 years