[kwin] [Bug 386021] Can not adjust the geometry of Kate

2017-10-21 Thread LinG 
https://bugs.kde.org/show_bug.cgi?id=386021

--- Comment #6 from LinG  ---
Or is there a way to call clientAdded() after the application has started up
instead of before?

Right now it goes:
- apply settings in kwin
- startup application -> applies settings from applications

result = applied settings in kwin are overwritten by application itself

Shouldn't it be?
- startup application -> applies settings from applications
- apply settings in kwin

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386021] Can not adjust the geometry of Kate

2017-10-21 Thread LinG 
https://bugs.kde.org/show_bug.cgi?id=386021

--- Comment #5 from LinG  ---
Also the workspace.getClient() function does not work for newly added clients
until the workspace.clientAdded() routine is finished, the client is not added
internally to the workspace. Which means that kwin does not manage newly added
applications yet until they are started up?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386021] Can not adjust the geometry of Kate

2017-10-21 Thread LinG 
https://bugs.kde.org/show_bug.cgi?id=386021

--- Comment #4 from LinG  ---
that was intentional in this example, if I had not done that and the second
script would work (which it doesn't) then you would not notice a difference in
the geometries.

Anyways, while trying out other applications I noticed that kate is by far not
the only application that does not listen to the settings that you apply
(spotify, inkscape, etc...)

My observation is that whatever you do inside the workspace.clientAdded
function does not always work, for a lot of applications they just ignore
whatever you tell them to do and create a geometry set by the application. 

This only happends during the startup of the application once it has already
been started up you can do whatever you want with the geometry using the API
that kwin provides. 

Shouldn't the clientAdded function overrule whatever the application itself
tries to achieve in terms of geometry and what not? Right now creating a Kwin
script that manages my newly added applications *consistently* is simply
impossible because most applications have their own predefined geometries.

Or is there a way to force the applications to adjust to the settings you apply
to it, that I'm unaware of?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386021] Can not adjust the geometry of Kate

2017-10-21 Thread Martin Flöser 
https://bugs.kde.org/show_bug.cgi?id=386021

--- Comment #3 from Martin Flöser  ---
just saying: your second script part has x/y and width/height swapped compared
to the working one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 386021] Can not adjust the geometry of Kate

2017-10-21 Thread LinG 
https://bugs.kde.org/show_bug.cgi?id=386021

--- Comment #2 from LinG  ---
But there are two different scenarios in which the application behaves
differently. Allow me to provide two small examples which illustrate what I'm
experiencing to be weird

case 1.

- open application: kate
- execute this piece of code in Kwin

var clients = workspace.clientList(); 
for (var i=0; i

[kwin] [Bug 386021] Can not adjust the geometry of Kate

2017-10-21 Thread Martin Flöser 
https://bugs.kde.org/show_bug.cgi?id=386021

Martin Flöser  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Martin Flöser  ---
That would be a problem in Kate then. Geometry is handled in truth by the
application. The window manager just tells the window "please take this
geometry". The window is allowed to just change it back.

Windows support a min size. You can check with xprop and xwininfo for the
minimum size and other constraints on the window. Maybe the geometry you want
to use just violates the constraints.

-- 
You are receiving this mail because:
You are watching all bug changes.