GitLab

REVIEW: 107317
BUG: 309170

Brian Nguyen authored Nov 07, 2012 and Martin Flöser committed Nov 10, 2012

This implements an optimization similar to one in compiz which defers updating
the backing X window during a window move until the move is terminated. This
helps alleviate some choppiness when using composite + vsync.

REVIEW: 107256

For clients w/o XSYNC support, limit resizes to 30Hz
to take pointless load from client and X11

REVIEW: 107087

REVIEW: 106960

The Compositor class actually behaves like a Singleton so it should be
one. Therefore four static methods are added:
* self() to access the Singleton
* createCompositor() to be used by Workspace to create the instance
* isCreated() to have a simple check whether the Singleton is already
  created
* compositing() as a shortcut to test whether the compositor has been
  created and is active

The isCreated() check is actually required as especially Clients might
be created and trying to access the Compositor before it is setup.

For most actions where the compositor needs to perform an action
(e.g. scheduling another repaint) signals were already emitted.
So it's easier to just connect the signals to the Compositor
which in turn makes the code much more readable.

All signals are connected from the Workspace when either the
Compositor gets constructed or a Toplevel gets created.

Arthur Arlt authored Aug 21, 2011 and Martin Flöser committed Aug 26, 2012

All Workspace functions which were implemented in the file composite.cpp
were moved to an own class Compositor. The header entries were moved as well.
All functions calls are updated.

QDesktopWidget::screenGeometry() fails if there's a panning or overlapping screen setup

REVIEW: 105974
BUG: 302783
FIXED-IN: 4.9.1

BUG: 303937
REVIEW: 105699

As discussed on the mailinglist [1] the tiling support is
removed from KWin. The main reasons for this step are:
* it is unmaintained
* it is a mode not used by any of the core KWin team
* original developer said at Akademy 2012 that he is not
  interested in picking up the work again
* tiling has quite some bugs, e.g. multi screen not supported
* is conflicting with other concepts in KWin, e.g. activities

There is ongoing work to get tiling supported through a KWin
script, which is a preferred way as it does not influence the
existing C++ code base.

[1] http://lists.kde.org/?l=kwin&m=133149673110558&w=2
BUG: 303090
FIXED-IN: 4.10
REVIEW: 105546

broke by accident with 33ffe901

BUG: 283302
REVIEW: 105360
FIXED-IN: 4.9rc1

BUG: 301805
CCBUG: 274466
FIXED-IN: 4.9

only conditionally break partial maximization on resizes and (by this) only partially adjust the restore size

BUG: 299647
FIXED-IN: 4.9
REVIEW: 104899

REVIEW: 104985
BUG: 300245
FIXED-IN: 4.9

CCBUG: 293011
REVIEW: 104073

tag window being moved before dropping out of QuickTile/Max and omit wobble if window being moved during maximization change

BUG: 222102
REVIEW: 104841
FIXED-IN: 4.9

BUG: 296097
REVIEW: 104293
FIXED-IN: 4.9

BUG: 298646
REVIEW: 104715
FIXED-IN: 4.9

CCBUG: 298646
REVIEW: 104702

remove some patch bodies
checkWorkspacePosition on geom_restore

CCBUG: 80265
reviewed-by: graesslin

The common usage of stacking order is to loop through
the list and find a specific Client. All these usages
still need to find a Client. For that the loops are
adjusted to first cast the Toplevel into a Client and
continue if the current item is no Client.

At the moment all entries in the stacking order should
still be Clients as the Deleted are not yet added.

BUG:  210926
FIXED-IN: 4.9
REVIEW: 104632

FEATURE: 124612
FIXED-IN: 4.9.0
REVIEW: 104457

Kephal has turned into not being more than a wrapper around
QDesktopWidget and does not even provide syntax sugar.

REVIEW: 104427

resetMaximize is done in changeMaximize since ages

BUG: 228815
REVIEW: 104347

REVIEW: 104215

cherry-picked from 0f3380f3
Conflicts:

	kwin/geometry.cpp
	kwin/scene.cpp

ratio:
it's the same preference in isFullScreenable, allows clients which do not withdraw their
restrictions (like aspect etc.) or get fullscreen artificially (like through kstart) to start in
"real" fullscreen mode.

BUG: 146741
REVIEW: 104331

BUG: 274466
REVIEW: 104233

there's no point in changing the behavior of the maximize button

BUG: 195576

BUG: 243423
REVIEW: 104236

store restore size /before/ removing the decoration for BorderlessMaximized (lead to window resizes on unmaximization)

BUG: 295449
REVIEW: 104185

REVIEW: 104080

REVIEW: 104010
CCBUG: 294211

This patch adds a new function Toplevel::addLayerRepaint, that in contrast
to addWorkspaceRepaint does not invalidate every blur texture cache that
overlaps with that region. As the name suggests it rather invalidates the
to the window associated layer at that position. This is especially useful
in the case of move/resize events in combination with oxygen-transparent,
where the altered window is almost always the topmost window and the blur
texture cache of the windows underneath are unchanged.

For the case of fully opaque windows the behaviour of addLayerRepaint
and addWorkspaceRepaint should be same.

REVIEW: 103906

BUG: 290959
BUG: 265160
BUG: 229292
BUG: 238279
BUG: 290758
BUG: 222831
BUG: 278275
BUG: 245747
BUG: 230000

BUG: 253697
BUG: 230570
BUG: 265977
BUG: 225337
BUG: 225339

REVIEW: 103855