aboutsummaryrefslogtreecommitdiffstats
path: root/client.c (unfollow)
Commit message (Collapse)AuthorLines
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
2013-12-11Add client wrapper for XWMHints to support XA_WM_HINTS in PropertyNotifyokan-8/+12
events; based off a diff from Thomas Adam.
2013-12-11Remove extra work and simplify client state handling.okan-14/+35
2013-12-11Stash Class and WM Hints in client_ctxokan-22/+17
2013-12-10Redraw client border when unhiding; during a hide, we just unsetokan-1/+2
the active flag but never redraw since it'll be in IconicState. Behaviour reported by sthen@
2013-11-27alter -r1.145 getsizehints to deal with clients that don't haveokan-36/+30
WM_NORMAL_HINTS.
2013-11-27simplify/unfoldokan-6/+4
2013-11-27Rewrite active/inactive client handling in client_setactive();okan-51/+29
client_leave() served no real purpose, likewise no reason to handle LeaveNotify events since an EnterNotify will process the next active client (and we don't have anything important to process anyway), so xev_handle_leavenotify() goes as well. Allows a simplification of client_mtf() and client_cycle_leave() for clarity. While here, unify a few client_current() checks. No intended behaviour change.
2013-11-12Alter the r1.35 of event.c race fix. Remove the forward looking eventokan-11/+2
queue check (removing the need for a server grab/ungrab) - if the client is going away, let it fall all the way through to a DestroyNotify event. There's no longer a need for us to manually destroy a client ourselves (removing yet another server grab/ungrab). Instead, when the UnmapNotify event is synthetic, simply set the state to Withdrawn (as per ICCCM), else Iconic (in our case 'hidden'). Verified with test case from the 2009 race which was the original reason for r1.35 of event.c.
2013-11-11Put back the border draw call in client_resize; since we are adding andokan-1/+3
removing the border on maximized clients we need to redraw. Also noticed by Tim van der Molen
2013-11-08stash WMProtocols in flagsokan-6/+6
2013-11-05quick keyboard focus fix for clients that neither populate wmhints nor ↵okan-2/+3
wmprotocols, like rdesktop; focus needs to be re-visited
2013-11-02The only reason we need to keep XSizeHints in our client_ctx is forokan-31/+38
flags, so just add one to hints; consolidates sizehints and shrinks. Additionally don't abuse PSize for XGetWMNormalHints() failures.
2013-11-01x/y from XSizeHints are obsolete (and have been for a long time), sookan-5/+3
instead use x/y from XWindowAttributes when USPosition|PPosition are set.
2013-11-01re-add support for WM_TAKE_FOCUS, and additionally this time only callokan-9/+18
XSetInputFocus() for clients that have the InputHint; latter fix discovered by Valery Masiutsin with a PoC patch - solves keyboard input focus loss for java apps.
2013-10-25A client_delete should behave differently depending on whether theokan-8/+10
triggering event was unmap (with pending destroy) log destroy; we only need to grab/ungrab the server lock, set WithdrawnState and XRemoveFromSaveSet clients coming from an unmap event - doing so for clients coming from destroy are already gone, hence we generate errors.
2013-10-20revert 1.138 (WM_TAKE_FOCUS) for nowokan-3/+1
2013-10-19Using xu_btn_ungrab() buttons during client_leave doesn't work (errorokan-6/+1
BadValue) when the modifier is already AnyModifier . Instead alter xu_btn_ungrab() to ungrab AnyButton/AnyModifier and call it only when a client is coming into focus in client_setactive(), instead of iterating over ignore mods - matches how we handle key grabs.
2013-10-19I believe we redraw the border in too many cases; likely a leftover fromokan-4/+1
the cc->pwin days - don't redraw on every unhide, resize, and mouse move/resize Expose event (note, all Expose events trigger a redraw anyway). Tested with some finicky X apps I could think of, though I'm sure others will find more - if so, and they 'lose' the border, please report!
2013-10-19For clients that support WM_TAKE_FOCUS in their WM_PROTOCOLS property, sendokan-1/+3
a ClientMessage event.
powered by cgit and git | oriole.systems | how to verify signatures