| Age | Commit message (Collapse) | Author | Files | Lines |
|
It seems to be a bit too early to drop support for this legacy protocol.
Xwayland apparently still relies on it for hardware acceleration as do
fairly recent mesa versions still in widespread use.
|
|
wlroots will now load xcursor themes at the correct scale automatically
based on the scale of the outputs where ther cursors are displayed.
Also make the error handling a bit more robust.
|
|
|
|
wl_drm is a legacy interface superseded by the linux-dmabuf
protocol. All clients should migrate.
This commit drops support for the protocol which should help find
whatever problematic clients are left in the wild.
If it turns out that this is too soon we can easily keep supporting
wl_drm for a little while longer as wlroots has not yet dropped support
for it.
|
|
|
|
|
|
|
|
This fixes a few issues with the XwaylandSurface bindings
|
|
|
|
|
|
|
|
We now send some protocol errors that wlroots 0.16 is missing [1].
This also allows us to access the xdg decoration from a view, which will
be necessary for some future changes.
[1]: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4051
|
|
|
|
|
|
|
|
|
|
These new functions allow testing commits without messing up the
pending state of the output and needing to rollback. The new apply()
function also makes the code considerably more concise.
|
|
|
|
|
|
It was forgotten to destroy the callback server side object when sending
the destructor event. With the new zig-wayland version, this cannot be
forgotten.
|
|
|
|
This commit is a breaking change as it drops support for the now
obsolete org_kde_kwin_idle protocol.
|
|
|
|
This should have been a compile error but slipped through due to a bug
in zig-wayland. This bug has now been fixed and the submodule updated.
|
|
This fixes a crash handling switch toggle events
|
|
|
|
This fixes the return type of Foo.fromWlrSurface() functions which can
in fact return null in the edge case that the role matches but the
corresponding object has already been destroyed.
|
|
This fixes a nasty ABI bug that could cause river to crash when
hotplugging down to 0 outputs.
|
|
|
|
e.g. `riverctl map -layout 0 normal Super Y spawn foot`
When this mapping is checked against a pressed key, layout 0 will be used to translate the pressed key instead of the currently active layout.
The number denotes to an index of the layouts set with
`XKB_DEFAULT_LAYOUT`.
|
|
This allows running a command on a laptop's lid being opened/closed
or a tablet's button/switch being pressed/toggled.
|
|
This is required for X11 input handling to work properly with
overlapping windows.
|
|
|
|
Since updating to wlroots 0.15 we can remove several workarounds we had
in place due to wlroots improvements.
|
|
|
|
The way wlroots handles the layer surface configure flow has changed a
bit and river's logic needs updating.
|
|
|
|
Currently wlroots sends use the drag destroy event before sending the
wl_data_device.leave event to the client, which makes things a bit
awkward. My patch fixing this has been merged to wlroots master so we
can remove this when upgrading to wlroots 0.15, but until then this
workaround will fix the issue.
|
|
Currently the implementation treats the x/y coordinates of
View.State.box as layout coordinates instead of output-relative. This
causes issues when using an output not at 0,0.
|
|
- add a new "urgent" border color
- add a new event to river-status-unstable-v1
Co-authored-by: Isaac Freund <ifreund@ifreund.xyz>
|
|
zig-wlroots now has this assert built in
This reverts commit 3392b21aa8982c1a9d5bf25307830a4294e5ae4c.
|
|
This will prevent people compiling river against the wrong wlroots
version and wondering why it crashes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|