aboutsummaryrefslogtreecommitdiffstats
path: root/client.c (follow)
Commit message (Collapse)AuthorAgeLines
* Start cleaning up name vs function differences; replace magic numbers.okan2015-11-10-4/+4
|
* Extend region to include both view and work areas; switch tookan2015-11-09-47/+49
| | | | | | | region_find() which no longer needs to recalculate gap each time a client (or menu) is created or altered. If no RandR, fall back to display dimensions while building regions instead of during execution.
* Only when mapping clients from an initial wm start or restart, query theokan2015-09-23-1/+11
| | | | | | | pointer and if it matches the child window, activate it; new clients will not need to make this roundtrip to the server. Based on a patch from Preben Guldberg.
* Mechanical change: group->gcokan2015-08-27-8/+8
|
* Add consistent checks against NULL.okan2015-08-27-5/+6
|
* Move client cycle grab/ungrab into a more relevant place; while here,okan2015-08-27-1/+5
| | | | update comments about why we need to grab/ungrab the keyboard.
* Split out sticky mode checks and the restoring of a client's group andokan2015-08-25-4/+12
| | | | | _NET_WM_DESKTOP from the config-based auto-grouping; no (intentional) behavior changes. Needed for further work in cleaning up this area.
* Implement _NET_CLIENT_LIST_STACKING (from Thomas Admin), butokan2015-08-24-1/+3
| | | | bottom-to-top order, as per spec (notified Thomas as well).
* Don't allow freeze operations on fullscreen (consistent with whatokan2015-08-24-1/+4
| | | | fullscreen does).
* Move CLIENT_STICKY logic from client hide/unhide to group hide/unhide;okan2015-08-23-7/+1
| | | | | rationale being that clients should be able to hide/unhide independently of group switching.
* Fix whitespace.okan2015-08-21-3/+3
|
* Add client freeze extension to _NET_WM_STATE Atom, allowing flag tookan2015-08-21-1/+3
| | | | persist. As usual with new Atoms, requires X restart.
* _NET_WM_STATE_STICKY implies only sticky at the group/desktop level, notokan2015-08-21-4/+4
| | | | position and size; based on discussion with a few.
* Bring group and client cycle closer together.okan2015-08-21-12/+12
|
* styleokan2015-07-01-5/+5
|
* Re-implement XClientMessage handling so that we can feed screen_find andokan2015-06-30-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.
* move client_find downokan2015-06-28-16/+16
|
* replace assert usageokan2015-06-28-4/+3
|
* Mechanical change from xinerama to region backed areas.okan2015-06-26-58/+58
|
* stash window dimensionsokan2015-06-08-1/+4
|
* fill in mwm definesokan2015-05-20-3/+3
|
* plug a leakokan2015-03-29-1/+2
|
* First restore net_wm_state(ewmh), then wm_state(iccc); prevents clientsokan2015-01-23-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.
* Switch to limits.h; replace MAXPATHLEN and MAXHOSTNAMELEN with PATH_MAXokan2015-01-19-2/+3
| | | | | | and HOST_NAME_MAX+1, respectively. ok doug@
* these have nothing to do with 'sticky', but rather group membership; rename.okan2014-09-27-2/+2
|
* these client actions are just toggles; less confusing with better namesokan2014-09-17-8/+8
|
* ewmh states _NET_WM_STATE_STICKY should not alter positionokan2014-09-17-4/+4
|
* don't toggle _WM_STATE_HIDDEN here yetokan2014-09-17-3/+3
|
* Implement EWMH _NET_WM_STATE_HIDDEN.okan2014-09-17-3/+14
|
* use similiar style for client flagsokan2014-09-15-5/+5
|
* fold in 'active' into 'flags'okan2014-09-10-6/+6
|
* move the check for an empty queue up during cycleokan2014-09-08-4/+2
|
* name the group client queue appropriately, like other queuesokan2014-09-08-6/+6
|
* more style nits and wrappingokan2014-09-08-5/+7
|
* since mruq has been folded in, rename mru-named functionsokan2014-09-08-7/+7
|
* Remove duplicate client queue (mruq); instead, remove and take theokan2014-09-08-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).
* more style nitsokan2014-09-07-18/+18
|
* screen_fromroot -> screen_findokan2014-09-07-2/+2
|
* Implement _NET_WM_STATE_STICKY, bound to CM-s by default; allows anyokan2014-08-25-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.
* Purely mechanical; unify 'num', 'no' and 'shortcut'.okan2014-08-20-2/+2
|
* Some clients set the urgency flag even if they are the active client;okan2014-02-06-2/+3
| | | | | 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-03-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.
* Move redundant window attr fetch from maprequest directly intookan2014-02-02-2/+5
| | | | client_init and perform that X roundtrip only once.
* move some init up and shed some blank linesokan2014-01-27-2/+1
|
* state is longokan2014-01-03-2/+2
|
* rename for clarityokan2014-01-02-5/+5
|
* When a client doesn't specify size hints, nothing prevents a resize tookan2014-01-02-1/+4
| | | | | | | 0x0 - don't allow this situation during mouse resize (check already in place for kbd resize). Reported by brynet@
* replace with memsetokan2013-12-17-3/+3
|
* Implement support for EWMH's _NET_WM_STATE_FULLSCREEN hint.okan2013-12-16-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@
* Teach screen_find_xinerama() to apply gap only when told to do so;okan2013-12-13-7/+7
| | | | adjust callers. Needed for an upcoming feature.
powered by cgit and git | oriole.systems | how to verify signatures