Age | Commit message (Collapse) | Author |
|
This reverts commit 8ed88822ca4448b06c2d7e6155d8022152b78017.
|
|
This reverts commit a11f2bbc7a4068321767bd7e8c7eee1aee278bc9.
|
|
This reverts commit 67896e9d8b98f679faf4456e26e82057c1884789.
|
|
This reverts commit 0ff13cf216056a36a261f4eed53c6a864989a9fb.
|
|
|
|
Hopefully this will help "future us" understand what's going on.
|
|
This functionality belongs in updatemons(), where it can hopefully be
written a bit more elegantly.
|
|
The wlr-output-management protocol requires that either all of the
changes from an apply request be applied successfully, in which case a
"succeeded" event is sent, or all of the changes are reverted and a
"failed" event is sent. As written, this could partially commit
changes, then fail.
Test the changes first (even for an "apply" event), then commit or
rollback as appropriate.
|
|
This should end up firing precisely when we need to adjust our geometry,
rather than us guessing about it based on requests.
|
|
|
|
|
|
|
|
Fix Initialization of NetWM Atoms
|
|
Additionally, variables xcursor and xcursor_mgr are only used
when xwayland is defined, so I make the variables declaration
contingent on whether xwayland is being used
|
|
|
|
No need to track our own order; wlroots has a reasonable default for us
already.
|
|
Define monitor's x,y at compile time
|
|
Tracking with breaking change in swaywm/wlroots#2593.
|
|
Replaces the outputOrder patch.
This avoids recalculating positions and allows to arrange monitors in
any order, not just from left to right.
The order in which monitors are defined in config.h still matters but
it's just the order in the list, not the actual position.
|
|
This reverts commit 90cc3b1e2c824db74e932dbb9733d398619a037c. Didn't
mean to merge this change.
|
|
This is the order of *_destroy calls which resulted in the fewest
errors/leaks detected by Valgrind. Most of the errors come from the
gbm_allocator code - will have to figure out which destroy call is still
missing.
|
|
|
|
This was a prime candidate for reducing the verbosity of some of our
code
|
|
|
|
Similar to Linux kernel approach, encapsulate some of the uglier
conditional compilation into inline functions in header files.
The goal is to make dwl.c more attractive to people who embrace the
suckless philosophy - simple, short, hackable, and easy to understand.
We want dwm users to feel comfortable here, not scare them off. Plus,
if we do this right, the main dwl.c code should require only minimal
changes once XWayland is no longer a necessary evil.
According to `cloc`, this also brings dwl.c down below 2000 lines of
non-blank, non-comment code.
|
|
|
|
|
|
Fix style.
|
|
Thanks so much for helping to keep the project running while life was
crazy!
|
|
#24 ensure that xwayland cursor defaults to left_ptr
|
|
|
|
Sway scale_box (rounding)
|
|
Fullscreen support
|
|
|
|
Layer shell
|
|
Added basic tap-to-click for touchpad users
|
|
When a new client is spawned, fullscreen isn't disabled for all clients
in that monitor any more.
Instead, all fullscreen clients are kept fullscreen, while other clients
spawn in the background.
When fullscreen is disabled, all clients are rearranged.
This is made to make dwl more flexible allowing multiple fullscreen
clients at the same time, have floating clients on top of a fullscreen
one and let stuff happen without quitting fullscreen, like many other
WMs and DEs.
|
|
Disable fullscreen on all visible clients in that monitor also before
enabling it on another client.
quitallfullscreen() is reintroduced becouse is now more useful
set c->isfullscreen later to avoid making quitallfullscreen() disable
fullscreen on the current client
|
|
|
|
|
|
The order in which monitors are defined in monrules[] actually matters.
Monotors that aren't configured in monrules[], it will always be the
leftmost.
|
|
...in internal calls to restore pointer focus. Necessary for the
unclutter patch, and there's no harm in avoiding this call even in
mainline; might prevents issues in same edge cases.
|
|
just wtf is XXX supposed to be? It sounds like a pornographic thing.
|
|
It's impossible to understand that this stands from drawable if you're
not familiar with dwm's code.
|
|
...or update selmon when we just want to restore pointer focus.
|
|
|
|
And don't activate clients while an overlay is focused.
|
|
Don't let internal calls to motionnotify(0) meant to update the pointer
focus from maplayersurfacenotify and destroylayersurfacenotify also
shift the keyboard focus to the surface under the cursor with
sloppyfocus.
|
|
Don't show an X cursor when closing an Xwayland window or with certain
dropdowns.
Based on https://github.com/djpohly/dwl/pull/32
|
|
The comment in this function's declaration says the backend is free to
ignore this setting, so maybe there's no need to make it configurable?
|