fix style on space-indented function
add some explanation of output reconfiguration
Hopefully this will help "future us" understand what's going on.
remove hacky code from output-management handler
This functionality belongs in updatemons(), where it can hopefully be
written a bit more elegantly.
commit entire output config, or fail and rollback
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.
Merge pull request #71 from djpohly/output-layout
call updatemons at the appropriate times
use updatemons as handler for output_layout.change
This should end up firing precisely when we need to adjust our geometry,
rather than us guessing about it based on requests.
unify increment style while we're here
remove unnecessary variable
cleanup on aisle createmon()
Merge pull request #80 from sam-barr/dwl_upstream
Fix Initialization of NetWM Atoms
Merge pull request #77 from djpohly/use-output-direction
Determine monitor order spatially
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
remove now-unneeded monitor position field
use output layout for dirtomon
No need to track our own order; wlroots has a reasonable default for us
already.
Merge pull request #72 from Stivvo/output-compile-set
Define monitor's x,y at compile time
remove EGL parameter from backend_autocreate
Tracking with breaking change in swaywm/wlroots#2593.
Define monitor's x,y at compile time
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.
flesh out cleanup
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.