This was caused by getTile returning null because the point we
checked (middle of the client) was offscreen.

Just move the client back in that case, though this should actually be
based on cursor position.

Unfortunately the pixmap issue did _not_ just happen when we violated
min/maxsize.

Among the clients that cause this issue are:

- Firefox

- Steam

vlc only causes problems on minsize.

When a client was desktop = -1 and moved to desktop = x, it wouldn't be
correctly removed from other desktops, resulting in empty space.

This cuts down on resizes, but still prevents pixmap issues.

This should hopefully never happen, but having a log message helps if it does.

This isn't needed with windowClosed, and causes a crash when closing a
fullscreen window that used to be tiled (and is therefore connected to
the signal)

This forces kwin to get a new pixmap and so prevents graphics bugs

This is called earlier, so we resize before FFM picks a new client.

NOTE: Find a better way to explain this

Purely bugfixes

* BladeLayout resizing
* Maximizing
* Fullscreen
* Documentation

This means moved windows once again go over them

This was broken by handling geometryChanged.

I can't get it to break now

Bugfix related to plasmoids immediately disappearing

Do this by not connecting windowShown to ignored clients (and also
removing that ineffective minimize hack)

Changes:

* Tabgroups
* Ignored clients don't stay below, just like manually floating ones
* Shortcut to swap tile with master (i.e. tileIndex 0)
* Bugfixes

Not sure wS is worth it, actually - I still get graphics issues with
e.g. steam

This is in line with what we do to clients that are set floating later on

This doesn't work currently as kwin seems to hand us the old screen size.

Appears to be working for now

This causes more problems than it solves (only part of the issues with steam)

This shouldn't actually happen

Ignored clients can't be tiled, ever - those properties don't change

Still sucks.

As Martin suggested - it really served no use in tilingmanager

This was caused by directly connecting the signal to the (desktop
specific) tiling object in a case of weird asymmetry.