Otherwise we still need mouse grabbing. Remove type variable, we can be smarter.

Such as ModifierKey+MouseButton. Also remove the unused type.

1. Completely remove decorOffsetMove and other related code from
   decor.cpp. Put the logic to handle the window->input () - window->border ()
   placement offset inside of setWindowFrameExtents instead. Now the window
   will always be offset from its original non-decorated position to the new
   decorated position, rather than having to guess between decoration sizes.
2. Make saveGeometry and restoreGeometry work relative to window->border ()
   as opposed to including it in the saved geometry. It is possible that the
   border size might change during maximization, as such, we don't want to
   save the position with the border before maximizing. Instead save the position
   as if it were never decorated so that when the window is restored it can be
   restored to its original position and then adjusted for its new border size.
3. Fix a few typoes in the tests.
4. Moved some commonly used matchers into compiz::testing
5. Make COMPIZ_PLUGIN_DIR accept multiple directories and look in each one
   of them for the plugin
6. Set COMPIZ_PLUGIN_DIR appropriately for each plugin that we wish to load
   on startup so that we load locally built plugins as opposed to installed
   ones.
7. Uncomment compiz_discover_tests for the acceptance tests. Now they are
   run by default.

Slightly improved long description of the move plugin
Removed <precision> settings as they just work for floats

Move code:
Introduced int moveIncrement to not have to execute
optionGetKeyMoveInc () to get the value twice

Implemented option to change the key move increment size
Removed hardcoded KEY_MOVE_INC

Implemented options to configure:

"Snapoff Distance"
"Snapback Semimaximized Windows"
"Snapback Distance"

Improved a few tooltips.

*Move code:

Replaced SNAP_BACK and SNAP_OFF hardcoded constants
Made those configurable

Implemented snapping back of horizontally maximized windows and fixed
the snapping for vertically maximized windows

Fixed a few wrong calculations in the if condition checks responsible
for snapping off and back

Merged if condition checks

Just calculate various values if we do not return false

Removed redundant brackets, fixed indentation, improved readability

Removed redundant brackets
Declaration and assignment of local variables in one line, if possible
Alignment and indentation fixes

to this branch and thus will be proposed seperately to reduce diff size
here

Implemented strategy to snap off horizontally semi-maximized windows by
dragging them along the x axis

Declare and assign variables in one line to improve readability

Implemented strategy to snap off horizontally semi-maximized windows

and all calls to it

Commented out calls to syncPosition in group plugin

It was causing a critical rendering regression (LP: #1089279).

It also caused a second strange regression where it was no longer possible
to safely revert 3513 (!?) without a causing a more severe regression of
LP: #1087193.

This basically "fixes" the various problems with nvidia being slow at
handling ConfigureWindow requests at the same time as doing synchronized
compositing, however it could come at the cost of some weird bugs. Keep
it off for now, and lets turn it on if there aren't any in testing

Problem: Editors like gedit and others will not recognize *.xml.in files as xml, so if opened there is no syntax highlighting making those files harder to read.
This commit fixes this by adding <?xml version="1.0" encoding="UTF-8"?> to all *.xml.in files in lp:compiz 

More fixes

in client code don't make any sense to keep

more sturdy abstraction

destructor, since plugins that make copies of CompOption::Value can cause actions to
be added through setOptionForPlugin and then those actions will be removed when the
value temporary goes away.

The action adding and removing only happens within the bounds of CompOption anyways, so
its its more appropriate to have it in its destructor.

Of course, this brings up another issue, which is that CompOption should be noncopyable
but this opens up a whole another can of worms.

How this even worked before is beyond me...

LP #931927

async model. Avoids feedback loops and all sorts of server/client confusion.
(LP: #923683)

positioning when it should be using lazy positioning (LP: #764330)

Split out paint scheduler into separate PaintScheduler class in the compiz::composite::scheduler namespace

have been loaded and also make CompositeScreen::registerPaintHandler
and CompositeScreen::unregisterPaintHandler wrapable so that plugins
know when the compositing state has changed

Fixes LP #874854