Merge pull request #25 from geistesk/error-maybe-uninitialized
getatom: fix potential uninitialized atom variable
focusclient checks whether oldsel == sel
No need to do it outside the call.
convert lastfocused() to focustop(m)
pass previous focus to focusclient
remove surface from focusclient function
Honestly not sure why a specific surface is focused rather than the
client figuring that out. Seems to work in a quick test, but we can
remember this commit if something breaks for, I dunno, mouse people.
C99 doesn't support anonymous unions
I'm cool with ->surface.xdg instead of ->xdg_surface though.
make setmon a bit more straightforward
simplify pointerfocus
Similar to focusclient
simplify focusclient
This arranges the function into some logical tasks: deactivate the old
client, update wlroots' keyboard focus, update our data structures, and
activate the new client. The last two only need to be done when
focusing something new, so an early return saves some horizontal space.
remove now-unused variables in focusclient
add tag bitset check from dwm
getatom: fix potential uninitialized atom variable
The getatom function returns the atom variable, which is only
initialized in case of a success. This results in a maybe-uninitialized
warning/error. After this commit, now a zero value is returned in case
of error.
attach_render and commit are all that's needed
attach_render tells the output that a "new" buffer has been prepared
(even if we haven't changed it). We need to call that and then commit
it to keep the render loop going.
Software cursors will freeze momentarily during layout updates, but I
suspect that this is not as easily fixed as it sounds. You can force
software cursors by running:
WLR_NO_HARDWARE_CURSORS=1 ./dwl
do not render frames when any surface has uncommitted resizes
Merge pull request #29 from alex-courtis/tidy-activate-notify
tidy activate notify resource