Bug 58064 - Smarter smart windows placement mode - more centered windows placement
Summary: Smarter smart windows placement mode - more centered windows placement
Status: RESOLVED DUPLICATE of bug 58063
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
Depends on:
Reported: 2003-05-03 16:30 UTC by Beat Fasel
Modified: 2019-06-30 23:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Beat Fasel 2003-05-03 16:30:41 UTC
Version:           0.95 (using KDE KDE 3.1.1)
Installed from:    Debian testing/unstable Packages
OS:          Linux

Currently, I'm using the centered windows placement mode, as my focus is usually in the middle of the screen and I don't feel comfortable of the currently implemented smart windows placement mode, as the latter tends to pop up windows in the periphery of the screen, e.g. in the upper left hand corner, which I find very annoying, because I have to move the window then more to the center.

Ok, why am I not completely happy then with the centered windows placement mode? Well, if you open two instances of the same program (e.g. two konqueror windows), the latter instance of konqueror perfectly covers the earlier one. With the centered mode, all windows are stacked up in the center, so one tends to forget about undelying covered windows.

I therefore propose a smarter "smart windows placement mode". What I mean by smarter is, that the windows should pop up very close to the center, but not cover each other completely as is possible with the centered mode. How close to the center is probably a matter of taste - maybe a parameter to be chosen by the user with an advanced configuration button?

Thanks for your attention!
Comment 1 Stephan Binner 2003-05-03 17:05:30 UTC
Dupe of 58063 
Comment 2 Nate Graham 2019-06-30 23:49:01 UTC

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