Age | Commit message (Collapse) | Author |
|
|
|
Update sizes for new EDID database.
|
|
Improve session handling
|
|
|
|
backend/drm: update EDID manufacturers database
|
|
|
|
|
|
backend/drm: reset gamma table on VT switch
|
|
|
|
|
|
Fix a crash on zxdg_decoration_manager_v1 destroy
|
|
When this request was called from a client, the unimplemented callback
was NULL and thus was crashing rootston.
|
|
gamma-control-v1: add missing destroy handler
|
|
|
|
Set b_lundef to false on FreeBSD in meson.build
|
|
|
|
This commit sets the required Meson version to >=0.48.0, and removes the
comment about building on FreeBSD requires an extra flag.
|
|
backend/drm: don't free connector immediately
|
|
xwayland/xwm: Stop including xcb_image.h
|
|
It's not used (XCB_IMAGE_FORMAT_Z_PIXMAP comes from xproto.h) and we
don't even have a pkg-config dependency on xcb-image, making the build
to fail on that inclusion on systems without the package.
|
|
When a pageflip is pending, we'll get a DRM event for the connector
in the future. We don't want to free the connector immediately
otherwise we'll use-after-free in the pageflip handler.
This commit adds a new state, "DISAPPEARED". This asks the pageflip
handler to destroy the output after it's done pageflipping.
|
|
Fix tablet_tool tilt and send proximity_out
|
|
Originally I asumed tilt_x and tilt_y are very unlikely to change
independent, I was proven wrong.
And while investigating Krita not using the Erasor tool, I found a bug,
which is unrelated though.
|
|
Implement pointer-constraints-unstable-v1 protocol
|
|
|
|
|
|
|
|
|
|
* Rename the constraint_create signal to new_constraint for
consistency
* Move the constraint_destroy signal to the constraint itself
* Use rotate_child_position instead of duplicating logic
* Fix inert constraint resource handling
* Style fixes
|
|
|
|
With Meson >=0.48.0 it is no longer necessary to pass the flag
"-D b_lundef=false" on FreeBSD.
|
|
The Meson option "b_lundef" need to be set to false on FreeBSD, because
the symbol "environ" is in crt1.o, which is not linked with shared
libraries. With Meson >=0.48.0 it is possible to set this option only
for FreeBSD. This patch changes meson.build to do that.
|
|
|
|
|
|
Fix unknown cursor in layer-shell example
|
|
|
|
Sessions can now be retrieved from a backend in a more general manner.
Multi-backend gets back its `session` field that contains the session
if one was created, removing the interfacing from multi backend with the
drm backend directly. This adds the possibility to use sessions even
without the drm backend.
It additionally fixes the bug that 2 session objects got created when
WLR_BACKENDS were set to "libinput,drm".
To allow vt switching without drm backend (and drm fd) on logind, start
listening to PropertiesChanged signals from dbus and parse the session
"Active" property when no master fd was created (this does not change
current drm backend behaviour in any way).
|
|
xwayland: Introduce set_decorations event
|
|
|
|
Fix partial dependency in protocol/meson.build
|
|
Apply multiseat fixes to FreeBSD direct backend
|
|
This commit applies the multiseat fixes that are part of PR #1063 (
commits 964e0a50 and 47895d2) to the FreeBSD direct backend.
|
|
External dependencies in Meson do not have include_directories,
therefore "includes: true" means nothing for the wayland-client partial
dependency. Because of this, the -I CFLAGs for wayland-client are not
used by the build command. This commit fixes this by using compile_args.
|
|
Introduce wlr_multi_for_each_backend
|
|
buffer: disconnect clients that commit an unknown buffer type
|
|
Disable hardware cursors when capturing output
|
|
|
|
If this happens, something went really wrong and we should do more
than just logging an error. See [1].
[1]: https://gitlab.freedesktop.org/wayland/weston/issues/148
|
|
Assert all the things!
|
|
pixman_region32_contains_point
I do not think the conversion is specifically defined, but on my system and SirCmpwn's
the floats are rounded instead of floored, which is incorrect in this case, since
for a range from 0 to 256, any value greater or equal to 0 and less than 256 is valid.
I.e. [0;256[, or 0 <= x < 256, but if x is e.g. -0.1, then it will be rounded to 0, which
is invalid. The correct behavior would be to floor to -1.
|