Using the default move constructor does not it work since it does
not re-register the event handlers with the new this-pointer. Instead
of implementing a custom move constructor, using std::unique_ptr<> is
the easier solution.

Closes #8

Closes #23

It is near impossible to implement the Wayland windowing system
reliably otherwise since the resolution is not changed immediately,
leading to a size mismatch between Kodi state and the windowing surface.

so it can safely be accessed from the main thread even when modes change

Needed when surface and buffer sizes are different on HiDPI displays

After calling ack_configure(), the compositor will assume that our
next attached buffer adheres to the size it requested (at least for
fullscreen surfaces). So we must make sure that this assumption holds,
or bad things will happen. Fix by delaying ack_configure() until
the egl context is reconfigured.

Closes #2

so that the opaque region matches the surface size that gets attached

…same

which should be done in waylandpp