| Age | Commit message (Collapse) | Author | Files | Lines |
|
This extends focus-output and send-to-output to allow targeting
outputs by name instead of relative position.
|
|
- alpine (musl)
- archlinux (glibc)
- freebsd
|
|
The name now includes the type, for the case of a physical device
advertising more than one logical device.
|
|
Device identifiers aren't so unique after all
|
|
This avoids a race where the fullscreen set is e.g. set then unset
before the transaction has been completed and the current state has
been updated.
|
|
In particular, this fixes a crash that can happen if a client is made
non-fullscreen and then, while that transaction is ongoing, made
fullscreen again.
|
|
I don't need anyone's permission to make this change since
GPL-3.0-or-later is one-way compatible with GPL-3.0-only.
|
|
|
|
|
|
Notably, we no longer call both wlr_output_test and wlr_output_commit
when applying an output config, which seems to fix or workaround an
occasional crash since updating to wlroots 0.15.0.
|
|
Currently river will place the surface at the top or left edge if
opposing anchors are set without a 0 width/height. Instead, center
the surface between the anchors.
|
|
Since the destroy() function may be called by river while the popup is
mapped, we must handle this case.
|
|
|
|
|
|
Fix X11 clients getting stuck minimized, and displaying a black screen
after they lose focus.
|
|
|
|
|
|
I personally made the mistake of using Alt instead of Mod1 when messing
with my config. This change makes things a bit more user
friendly/intuitive.
|
|
|
|
We currently don't properly handle xdg surface geometry of the parent,
which causes popups to render partially off-screen in some cases.
GTK4 clients such as easyeffects seem to trigger this issue reliably.
|
|
|
|
Since Zig 0.9 @tagName() and other similar builtins return 0 terminated
data.
|
|
I thought this should be fine as river won't yield to the event loop
when Seat.deinit() is called before the wlroots seat is destroyed, but
a segfault on exit has been reported with a stack trace mentioning
wlr_seat_destroy(). Let's hope this clears that up.
|
|
This is required for X11 input handling to work properly with
overlapping windows.
|
|
There are a couple of TODOs here that are not worth resolving until
after moving to the scene graph api.
|
|
|
|
|
|
|
|
Since updating to wlroots 0.15 we can remove several workarounds we had
in place due to wlroots improvements.
|
|
Subsurfaces may already be mapped when create is called, in which case
we must add the commit listener.
|
|
The new code to dedup XcursorManager.setCursorImage() calls for
efficiency currently doesn't handle clients setting the cursor properly.
This commit corrects this oversight.
|
|
|
|
The way wlroots handles the layer surface configure flow has changed a
bit and river's logic needs updating.
|
|
wlroots doesn't avoid re-setting the same cursor image so this is
relatively expensive to call repeatedly if nothing has changed.
|
|
|
|
We always pass the result of this to mem.span() currently, no need for
the code duplication.
|
|
This patch allows to focus outputs by clicking on the empty background and by
clicking on layer surfaces without keyboard interactivity. This makes it
possible to use the cursor to focus outputs with no visible views.
This also fixes problems with pointer interactive layer surfaces (for example
launchers and docks) on non-focused outputs.
|
|
|
|
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.
|
|
|
|
We used to look in /etc/river/init if no init at ~/.config/river/init
or $XDG_CONFIG_HOME/river/init was found but this feature was
removed. It seems that we forgot to remove this mention of the old
behavior however.
|
|
|
|
|
|
|
|
|
|
|
|
We haven't managed to keep this at all up to date, which defeats the
purpose. Please refer to the git history for a complete list of
contributors.
|
|
|
|
|
|
This doesn't really matter that much as unrecognized options will still
trigger a help message to be printed, but -h is much more standard so
lets make the predictable choice here while sticking to only single '-'
flags.
|