aboutsummaryrefslogtreecommitdiffstats
path: root/client.c (unfollow)
Commit message (Collapse)AuthorLines
2015-08-25Split out sticky mode checks and the restoring of a client's group andokan-4/+12
_NET_WM_DESKTOP from the config-based auto-grouping; no (intentional) behavior changes. Needed for further work in cleaning up this area.
2015-08-24Implement _NET_CLIENT_LIST_STACKING (from Thomas Admin), butokan-1/+3
bottom-to-top order, as per spec (notified Thomas as well).
2015-08-24Don't allow freeze operations on fullscreen (consistent with whatokan-1/+4
fullscreen does).
2015-08-23Move CLIENT_STICKY logic from client hide/unhide to group hide/unhide;okan-7/+1
rationale being that clients should be able to hide/unhide independently of group switching.
2015-08-21Fix whitespace.okan-3/+3
2015-08-21Add client freeze extension to _NET_WM_STATE Atom, allowing flag tookan-1/+3
persist. As usual with new Atoms, requires X restart.
2015-08-21_NET_WM_STATE_STICKY implies only sticky at the group/desktop level, notokan-4/+4
position and size; based on discussion with a few.
2015-08-21Bring group and client cycle closer together.okan-12/+12
2015-07-01styleokan-5/+5
2015-06-30Re-implement XClientMessage handling so that we can feed screen_find andokan-2/+3
client_find valid resources as needed, relieving the need for screen_find to ungracefully handle invalid root windows. Removes a long standing XXX. Should theoretically allow XClientMessage handling on more than one X screen. Alter callers of screen_find to handle failures.
2015-06-28move client_find downokan-16/+16
2015-06-28replace assert usageokan-4/+3
2015-06-26Mechanical change from xinerama to region backed areas.okan-58/+58
2015-06-08stash window dimensionsokan-1/+4
2015-05-20fill in mwm definesokan-3/+3
2015-03-29plug a leakokan-1/+2
2015-01-23First restore net_wm_state(ewmh), then wm_state(iccc); prevents clientsokan-7/+6
from re-hiding on restart due to flag toggling (note that this is ripe for re-vamping). Behavior only observed on restarts. Problem found by, and initial patch from, Henri Kemppainen (thanks!), though ever so slightly different one applied.
2015-01-19Switch to limits.h; replace MAXPATHLEN and MAXHOSTNAMELEN with PATH_MAXokan-2/+3
and HOST_NAME_MAX+1, respectively. ok doug@
2014-09-27these have nothing to do with 'sticky', but rather group membership; rename.okan-2/+2
2014-09-17these client actions are just toggles; less confusing with better namesokan-8/+8
2014-09-17ewmh states _NET_WM_STATE_STICKY should not alter positionokan-4/+4
2014-09-17don't toggle _WM_STATE_HIDDEN here yetokan-3/+3
2014-09-17Implement EWMH _NET_WM_STATE_HIDDEN.okan-3/+14
2014-09-15use similiar style for client flagsokan-5/+5
2014-09-10fold in 'active' into 'flags'okan-6/+6
2014-09-08move the check for an empty queue up during cycleokan-4/+2
2014-09-08name the group client queue appropriately, like other queuesokan-6/+6
2014-09-08more style nits and wrappingokan-5/+7
2014-09-08since mruq has been folded in, rename mru-named functionsokan-7/+7
2014-09-08Remove duplicate client queue (mruq); instead, remove and take theokan-17/+18
global Clientq and place it inside screen_ctx since every client belongs to a screen, then use the same per screen clientq to track stacking order (the sole reason for mruq).
2014-09-07more style nitsokan-18/+18
2014-09-07screen_fromroot -> screen_findokan-2/+2
2014-08-25Implement _NET_WM_STATE_STICKY, bound to CM-s by default; allows anyokan-1/+18
client to 'stick' to all desktops (ewmh speak) or groups - this currently has the same affect as setting a client's group to 'nogroup', with the exception that the client can also be in a group, so when un-sticking, the client will go back to its original group/desktop.
2014-08-20Purely mechanical; unify 'num', 'no' and 'shortcut'.okan-2/+2
2014-02-06Some clients set the urgency flag even if they are the active client;okan-2/+3
prevent annoying behavior by only setting the cwm urgency flag if the client is not active; diff from Thomas Adam.
2014-02-03Move redundant bits from screen_init (while dealing with existingokan-3/+11
clients) directly into client_init, performing the X roundtrip only once. With the previous change in maprequest, this moves decision making into one place for creating new clients.
2014-02-02Move redundant window attr fetch from maprequest directly intookan-2/+5
client_init and perform that X roundtrip only once.
2014-01-27move some init up and shed some blank linesokan-2/+1
2014-01-03state is longokan-2/+2
2014-01-02rename for clarityokan-5/+5
2014-01-02When a client doesn't specify size hints, nothing prevents a resize tookan-1/+4
0x0 - don't allow this situation during mouse resize (check already in place for kbd resize). Reported by brynet@
2013-12-17replace with memsetokan-3/+3
2013-12-16Implement support for EWMH's _NET_WM_STATE_FULLSCREEN hint.okan-24/+38
Since we already have a form of 'maximize', we need to differentiate between 'maximize' and the new 'fullscreen' mode. The 'maximize' mode will continue to honor gap but now *retains* the border, matching the 'vert/horz maximize' behaviour. The new 'fullscreen' mode supports and follows the _NET_WM_STATE_FULLSCREEN hint, allowing the client perform additional window modifications; in this mode, cwm(1) will *ignore* gap, remove borders and freeze(move/resize) the client. Additionally, 'fullscreen' mode will remember various combinations of previous states. * default keybinding changes: CM-f 'fullscreen', CM-m 'maximize' (re-map as desired). Positive feedback from a few, testing and ok sthen@
2013-12-13Teach screen_find_xinerama() to apply gap only when told to do so;okan-7/+7
adjust callers. Needed for an upcoming feature.
2013-12-13we need the save-set when re-exec'ing so as to not lose State on our hidden ↵okan-1/+3
clients
2013-12-13Add support for XUrgency and matching _NET_WM_STATE_DEMANDS_ATTENTIONokan-1/+14
ewmh hint; urgencyborder is configurable. The urgency flag will stick, even while on a client in a non-viewable group, until the client receives focus (where the border is reset). Initial diff from Thomas Adam with some changes/enhancements from me.
2013-12-12ICCCM explicitly states that server time (CurrentTime) should *not* beokan-5/+8
used for focus events, but rather the timestamp of the generated event. Track the last event timestamp and send it down for a WM_TAKE_FOCUS ClientMessage. I suspect we should do this for clients that don't announce this Atom as well, though the raciness gets us into a bind. Solves focus order issue since WM_TAKE_FOCUS; fix verified by sthen@ ok sthen@
2013-12-11we don't need to manage the save-set since we're not reparenting; left-over ↵okan-3/+1
from pwin
2013-12-11since we are drawing in unhide, no need to during client setupokan-2/+1
2013-12-11apply mwm hints laterokan-4/+4