| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Fix compiler errors.
|
|
- Some platforms don't expose kill() unless _POSIX_C_SOURCE is defined.
- fork(), execl(), and setsid() need unistd.h on some platforms.
Basically, this fixes some platform-specific build errors.
|
|
Separate root-related code
|
|
|
|
This creates a root.c and moves bits and pieces from elsewhere into it.
* layout_init has been renamed to root_create and moved into root.c
* root_destroy has been created and is called on shutdown
* scratchpad code has been moved into root.c, because hidden scratchpad
containers are stored in the root struct
|
|
Check correct ws for sticky and fix floating iter
|
|
|
|
Show swaynag on config errors
|
|
|
|
|
|
|
|
|
|
Add missing stdlib.h includes to swaynag
|
|
|
|
Fix crash when fullscreen view closes on inactive workspace
|
|
Fix crash when moving cursor over a fullscreen split container
|
|
Deny "move container" when an empty workspace is focused
|
|
Calling container_at_view fails an assertion if the container isn't a
view. Calling tiling_container_at works correctly, as that function
checks if the container is a view and calls container_at_view if so.
|
|
When a view unmaps, normally the surviving ancestor (ie. after reaping)
needs to be arranged. When a fullscreen view unmaps, it arranges the
workspace rather than the surviving ancestor, but didn't handle cases
where the workspace itself was reaped. This happens if the workspace is
not currently shown and the fullscreen view was the last container on
that workspace.
This commit rewrites this part of view_unmap so it's more readable, and
fixes the crash by not arranging the workspace if it's been reaped. Note
that it no longer arranges the output under any circumstance - this
wasn't required anyway.
|
|
|
|
Change exit binding in default config to nag user, matching i3
|
|
|
|
Enable wlr-gamma-control-unstable-v1
|
|
|
|
Fix pointer events for fullscreen views
|
|
|
|
Fix crash on mouse motion on fullscreen container
|
|
container_at expects a workspace, not the fullscreened container.
Fixes #2409
|
|
|
|
Fix popups v3
|
|
|
|
This reverts commit 9aa258d33a9baa42895214da7e82f4568fcb8f76.
Reverting the revert, so that popups can be fixed.
|
|
Implement swaynag
|
|
|
|
This reverts commit de86d65627e96cffe77f4abf11c4a0b982326ff9.
|
|
Allow moving containers when workspace itself is focused
|
|
Fix race condition crashes when unmapping views
|
|
Fix focus related crashes
|
|
Reset signal mask after fork
|
|
* seat_set_focus_warp lacked a container NULL check
* view mapping code needs to use seat_get_focus_inactive
Also, seat_set_focus_warp triggered the wrong IPC event if focus was a
workspace, which resulted in swaybar not showing the workspace as
active.
|
|
wlroots uses wl_event_loop_add_signal to handle SIGUSR1 from Xwayland.
wl_event_loop_add_signal works by masking the signal and receiving it from a
signalfd. The signal mask is preserved across fork and exec, so subprocesses
spawned by Sway start with SIGUSR1 masked. Most subprocesses do not expect this
and never unmask the signal, resulting in missing functionality or unexpected
behavior for processes that use SIGUSR1 (such as i3status).
Fix this by unmasking all signals between fork and exec.
|
|
|
|
This fixes two issues which were both introduced in #2396.
First issue:
The PR changes the location of the buffer save to transaction_apply, but
puts it inside the should_configure block. For unmapping (destroying)
views, should_configure returns false so it wasn't saving the buffer. If
a frame was rendered between the unmap and the transaction applying then
it would result in a crash.
Second issue:
If a destroying view is involved in two transactions, we must not
release the buffer between the transactions because there is no live
buffer to grab any more.
|
|
* Link xcb dependency to meson options "enable_xwayland"
* Link xcb dependency to meson options "enable_xwayland"
|
|
Correctly track saved surfaces during multiple transactions
|
|
|
|
|
|
|
|
|
