Bug 132347

Summary:	window or application specific settings should allow relative geometry values
Product:	[Plasma] kwin	Reporter:	Roman Fietze <kde>
Component:	rules	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	REOPENED ---
Severity:	wishlist	CC:	alpeterson, bwpearre, natalie_clarius, spamless.9v5xj, tl1234562004, torquil
Priority:	HI	Keywords:	junior-jobs
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Roman Fietze 2006-08-13 16:18:37 UTC

Version:            (using KDE KDE 3.5.4)
Installed from:    SuSE RPMs

The geometry switch or property normally allows to specify the positions of windows relative to any of the four edges of the window. A positive value defines the distance from left or top, a negative value defines the distance from bottom or right.

The kwin window or application specific setting should do the same.

This will be necessary when I e.g. locate small utility windows at the right or bottom edge of my desktop. Thos positions are always stored as positive distances from top left. When I now switch X terminals (servers) that have larger or smaller screens, those windows hang around in the middle of nowhere or are crushed to either border of the desktop.

Comment 1 Lubos Lunak 2006-08-15 15:16:05 UTC

*** Bug 95099 has been marked as a duplicate of this bug. ***

Comment 2 Branan 2006-10-22 23:14:51 UTC

hmm... I suppose comparing distance from [top of window]->[top of screen] and [bottom of window]->[bottom of screen], using the smaller, and saving that. The same with [left] and [right]. Positive values would be interpreted as starting from [top] or [left], and negative from [bottom] or [right]. The only issue would be if unsigned integers are currently being used... That could mess things up, if someone happens to have a window more than 2 billion pixels from the edge of the screen (Which shouldn't happen... But as soon as you say something "shouldn't happen", Murphy goes and gets himself involved)

Comment 3 Roman Fietze 2006-10-23 16:57:30 UTC

> if someone happens to have a window more than 2 billion pixels

This is only almost as possible as having somebody with a screen 4 billion pixels wide or high.

X11 geometry specifications work that way, why shouldn't work KDE geometry specifications work that way?

Comment 4 Lubos Lunak 2007-01-26 17:46:41 UTC

*** Bug 135917 has been marked as a duplicate of this bug. ***

Comment 5 Lubos Lunak 2007-04-24 15:07:02 UTC

*** Bug 144314 has been marked as a duplicate of this bug. ***

Comment 6 Roman Fietze 2009-09-30 20:54:20 UTC

Plasma still has the same problem.

This is a similar problem as Bug 188728. People do not seem to use different X servers very often, but Linux/UNIX/X11 is not Windows, so many of my friends, colleagues and I do.

Comment 7 Roman Fietze 2009-11-20 13:54:20 UTC


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

Comment 8 Martin Flöser 2009-11-20 14:07:41 UTC

*** Bug 215415 has been marked as a duplicate of this bug. ***

Comment 9 Aaron Peterson 2012-04-05 07:17:31 UTC

I think this is the bug that causes Krunner to fill the whole screen.

Comment 10 Thomas Lübking 2012-04-05 09:13:58 UTC

@aaron
i think you're wrong - or posted to the wrong bug ;-)

this here is a very specific request to allow to define forced screen geometry as relative values (ie "20,-250" means 20px from the left and 250px  from the bottom)
even if you had a rule for krunner you'd by this only move it out of screen (and i guess even that should be prevented, but am not sure whether rules are restricted in positioning as well)

Comment 11 Thomas Lübking 2013-10-12 19:51:20 UTC

*** Bug 320908 has been marked as a duplicate of this bug. ***

Comment 12 Thomas Lübking 2013-10-12 19:51:53 UTC

And this is not  a junior job