| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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.
|
|
|
|
This is likely more clear than "layout client" to most users.
|
|
|
|
|
|
mpv for example has key bindings to set the window size to a multiple of
the video resolution. This is a valid use case for client-size resizing
of the view and river should respect this if the view is floating.
|
|
This seems to fix an issue with mouse input for steam if steam is not
started on an output at 0,0. X11 is pretty spooky.
|
|
|
|
This greatly improves the UX of this feature, as views moving under a
stationary cursor (as happens during the zoom command for example) will
no longer trigger focus change.
|
|
|
|
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.
|
|
This avoids needing to run pwayland's scanner with root privileges and
install the river-layout bindings to system directories.
|
|
|
|
|
|
xkbcommon uses `Return` to indicate this key, `Enter` isn't a valid keysym name.
Co-authored-by: Euro <no>
|
|
Layout generators are generally pretty fast. The timeout is only reached when
the generator is faulty / stuck. In that case, freezing for 1 second is simply
bad UX.
|
|
The input manager and seats must be destroyed before the display is
destroyed as they need to destroy their timer event sources used for key
repeat.
|
|
Currently the view destruction sequence is started as soon as a view
is unmapped. However, this is incorrect as a client may map the view
again instead of destroying it.
Instead, only start the view destruction sequence when the underlying
xdg toplevel or xwayland surface is destroyed.
|
|
|