[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 325286] snap-to-client vs snap-to-deco should be configurable
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2014-04-18 10:58:08
Message-ID: bug-325286-17878-SBW0LD1FsR () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=325286

--- Comment #77 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to comment #70)
> > The problem is that I find snap-to-client incompatible with active borders.
> What's "active borders" to you?

Electric borders - like on inner edges, the edge looses its special value
(eventually to the electric border)
Unlike inner edges, there's no bleeding, so the snap position becomes
indifferent (where i would personally probably not want to snap to that edge,
but some px away from it - if at all)


(In reply to comment #72)
> multiple ways: better scripting support to influence the snapping behavior
> or giving the decoration plugin more control over snapping.

I don't see where moving it to the decoration would get us rid of the option
(or lower the code branch which is merely an assignment of 4 integers anyway) -
the checkbox would be in the deco config then.
The decoration should (like on quick tiling) be informed about: "you're gonna
be snapped to that edge, wanna re-layout?"

The solution will likely be some movecontrol script class which client
movements are piped through (for an edge snapping subcategory depending on the
distance from outer screen borders, so they don't have to calculate that)
unconditionally.
This will allow to treat different clients or edges differently, also keep
random distances from the borders etc. and also (for the general move control) 
to snap to certain screen regions or positions (instead of "center")

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]