Merge pull request #49 from guidocella/layer-shell

Layer shell

use the install command to install

Merge pull request #65 from Keating950/master

Add install target to Makefile

Merge pull request #56 from oyren/readme_log

remove log flags from readme

Merge pull request #62 from Java-boi/master

Added basic tap-to-click for touchpad users

Merge pull request #66 from richardipsum/master

fix undeclared WLR_KEY_PRESSED

fix undeclared WLR_KEY_PRESSED

add install target to Makefile and corresponding prefix variable to config.mk

Added support for natural scrolling

Added basic tap-to-click for touchpad users

remove log flags from readme

The following commit has removed the logs but they are still in the readme.
3b1992ca91b9a468019165c985263f5b1cc78c2c">https://github.com/djpohly/dwl/commit/3b1992ca91b9a468019165c985263f5b1cc78c2c

extract function and comment it

remove braces

fix multi monitors even more

When a monitor is created or removed, the geometries of the old ones
must be updated. This is also more efficient than before since we
calculate the monitor geometries only when creating and destroying
monitors. arrangelayers() is needed to recalculate m->w. arrange() is so
clients don't move to the left monitor when plugging or unplugging
monitors (clients keep the same coordinates but the field below them
changes).

simplify

fix multi monitors further

Fix layer surfaces without an exculsive area by using the right x and y
for the current monitor (by Stivvo).

remove unneeded line

The bug was caused by usable_area's x and y not being set in
arrangelayers. For example if on a 2nd HD monitor, x should be 1920
while the first one ends at 1919. So I don't see why m->m should be
recalculated after creating the monitor.

try to fix again

Calculate x and y of usable_area, not just width and heigth.

fix multi monitors

If you don't recalculate the monitor's geometry before arranging,
clients get arranged in the first monitor. I don't understand why this
fixes the bug since tile() uses m->w rather than m->m, nor why it needs
to be recalculated after creating the monitor but sway does it too.

Although not necessary to fix the bug I also made arrangelayer() do like
sway again and recalculate usable_area instead of reusing m->m, since
m->m seems to be incorrect until it gets recalculated shortly after in
arrange(), so I suspect that leaving usable_area = m->m will cause
issues under certain circumstances.

Someone with a multi-monitor setup or better knowledge of Wayland may be
able to figure out the cause of the bug. For now, this makes layer shell
work.

remove variable