summary refs log tree commit diff
path: root/client.c
Commit message (Collapse)AuthorAgeFilesLines
* Purely mechanical; unify 'num', 'no' and 'shortcut'.okan2014-08-201-1/+1
|
* Some clients set the urgency flag even if they are the active client;okan2014-02-061-1/+2
| | | | | prevent annoying behavior by only setting the cwm urgency flag if the client is not active; diff from Thomas Adam.
* Move redundant bits from screen_init (while dealing with existingokan2014-02-031-2/+10
| | | | | | 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.
* Move redundant window attr fetch from maprequest directly intookan2014-02-021-1/+4
| | | | client_init and perform that X roundtrip only once.
* move some init up and shed some blank linesokan2014-01-271-1/+0
|
* state is longokan2014-01-031-1/+1
|
* rename for clarityokan2014-01-021-4/+4
|
* When a client doesn't specify size hints, nothing prevents a resize tookan2014-01-021-0/+3
| | | | | | | 0x0 - don't allow this situation during mouse resize (check already in place for kbd resize). Reported by brynet@
* replace with memsetokan2013-12-171-2/+2
|
* Implement support for EWMH's _NET_WM_STATE_FULLSCREEN hint.okan2013-12-161-23/+37
| | | | | | | | | | | | | | | | 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@
* Teach screen_find_xinerama() to apply gap only when told to do so;okan2013-12-131-6/+6
| | | | adjust callers. Needed for an upcoming feature.
* we need the save-set when re-exec'ing so as to not lose State on our hidden ↵okan2013-12-131-0/+15
| | | | clients
* ICCCM explicitly states that server time (CurrentTime) should *not* beokan2013-12-121-4/+7
| | | | | | | | | | | 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@
* we don't need to manage the save-set since we're not reparenting; left-over ↵okan2013-12-111-2/+0
| | | | from pwin
* since we are drawing in unhide, no need to during client setupokan2013-12-111-1/+0
|
* apply mwm hints laterokan2013-12-111-3/+3
|
* Add client wrapper for XWMHints to support XA_WM_HINTS in PropertyNotifyokan2013-12-111-7/+11
| | | | events; based off a diff from Thomas Adam.
* Remove extra work and simplify client state handling.okan2013-12-111-13/+34
|
* Stash Class and WM Hints in client_ctxokan2013-12-111-21/+16
|
* Redraw client border when unhiding; during a hide, we just unsetokan2013-12-101-0/+1
| | | | | | the active flag but never redraw since it'll be in IconicState. Behaviour reported by sthen@
* alter -r1.145 getsizehints to deal with clients that don't haveokan2013-11-271-35/+29
| | | | WM_NORMAL_HINTS.
* simplify/unfoldokan2013-11-271-5/+3
|
* Rewrite active/inactive client handling in client_setactive();okan2013-11-271-50/+28
| | | | | | | | | | | 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.
* Alter the r1.35 of event.c race fix. Remove the forward looking eventokan2013-11-121-10/+1
| | | | | | | | | | | | 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.
* Put back the border draw call in client_resize; since we are adding andokan2013-11-111-0/+2
| | | | | | removing the border on maximized clients we need to redraw. Also noticed by Tim van der Molen
* stash WMProtocols in flagsokan2013-11-081-5/+5
|
* quick keyboard focus fix for clients that neither populate wmhints nor ↵okan2013-11-051-1/+2
| | | | wmprotocols, like rdesktop; focus needs to be re-visited
* The only reason we need to keep XSizeHints in our client_ctx is forokan2013-11-021-30/+37
| | | | | flags, so just add one to hints; consolidates sizehints and shrinks. Additionally don't abuse PSize for XGetWMNormalHints() failures.
* x/y from XSizeHints are obsolete (and have been for a long time), sookan2013-11-011-4/+2
| | | | | instead use x/y from XWindowAttributes when USPosition|PPosition are set.
* re-add support for WM_TAKE_FOCUS, and additionally this time only callokan2013-11-011-8/+17
| | | | | | 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.
* A client_delete should behave differently depending on whether theokan2013-10-251-7/+9
| | | | | | | 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.
* revert 1.138 (WM_TAKE_FOCUS) for nowokan2013-10-201-2/+0
|
* Using xu_btn_ungrab() buttons during client_leave doesn't work (errorokan2013-10-191-5/+0
| | | | | | | 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.
* I believe we redraw the border in too many cases; likely a leftover fromokan2013-10-191-3/+0
| | | | | | | | | 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!
* For clients that support WM_TAKE_FOCUS in their WM_PROTOCOLS property, sendokan2013-10-191-0/+2
| | | | a ClientMessage event.
* unify type; no changeokan2013-10-031-1/+1
|
* collapse linesokan2013-07-151-2/+1
|
* simplify atom handling; allows us to limit to one round-trip to serverokan2013-07-151-6/+6
| | | | for gathering Atoms.
* move synthetic responses and have client_msg only work with WM_PROTOCOLS,okan2013-06-101-5/+40
| | | | since that's all ClientMessageEvent is for anyway.
* alter conf_grab(_kbd) to first ungrab AnyKey/AnyModifier, then proceedokan2013-05-231-1/+1
| | | | | | | | to grab keys in keybindingq. we don't need to ungrab/grab on every addition to the queue, just once with a complete keybindingq; simplify grabbing keys per screen (during init) and during a MappingNotify. while here, change conf_grab_{kbd,mouse} to require only a Window.
* add support for _NET_WM_STATE_MAXIMIZED_{HORZ,VERT}; from Alexander Polakov.okan2013-05-201-0/+5
| | | | | while I'm unsure of the final look of _NET_WM_STATE, there's no reason to delay this support.
* - switch border colors to Xftokan2013-05-191-4/+4
| | | | | | | | | - merge border/menu color structures/functions since they now both use Xft - switch xu_xorcolor to operating on XftColor instead of just XRenderColor (basically adding pixel) - if color name allocation fails, revert back to default (this, along with font validation should occur during config parse, but we don't have screens setup yet - likely to change at some point)
* use XGetWMProtocols and simplify WM_PROTOCOL handlingokan2013-05-191-18/+15
|
* new -> initokan2013-05-111-1/+1
|
* remove group in client_delete directly.okan2013-05-061-3/+3
|
* mechanical xu_{get,set}state -> xu_{get,set}_wm_state changeokan2013-04-171-5/+5
|
* slightly rework WM_STATE set/get to make it less ambigious; will be more clearokan2013-04-171-7/+11
| | | | on what needs to change to make it right in the end.
* only a window is required to set WM_STATE. also un-confuse xu_ptr_getposokan2013-04-141-1/+1
| | | | | by using 'win' instead of 'rootwin' so as not to imply only the root window is queried, rather any window.
* we handle WM_STATE here, so remove misleading comment.okan2013-04-121-1/+0
|
* we already set window state in client_hide or client_unhide right before, sookan2013-04-121-1/+0
| | | | there's no need to do it again.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-07 12:04:36 +0000