| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Remove `.git` suffix from river repo in `sources` section as the
suffix make the ci only clone the repo. Without the suffix the ci
checkout the correct commit to build river.
We don't need to remove the suffix from others sources as cloning
the repo and checkout the tag version we want is enough.
|
|
The motivation for this change is to simplify the implementation
and remove a massive footgun that is currently present and causing
UB/crashes. If a layer surface is destroyed in arrangeLayers() then
the code in LayerSurface.handleCommit() after the arrangeLayers()
call accesses free'd memory. This is of course possible to fix,
but it's far simpler to loosen up the protocol implementation a bit.
The new implementation is also in line with what sway and the new
wlroots layer shell helper do and is perfectly valid according to
the protocol.
|
|
|
|
I have encountered a crash (failing assert) if a view specified a fixed
size less than this minimum, and according to ifreund this behavior was
planned to be removed, anyway.
|
|
|
|
|
|
|
|
user defined values
|
|
|
|
|
|
|
|
|
|
|
|
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.
|