aboutsummaryrefslogtreecommitdiffstats
path: root/kbfunc.c (unfollow)
Commit message (Collapse)AuthorLines
2019-02-22Rename internal functions to delinate between client remove, delete and xprotookan-3/+3
delete; 'window-close' is now the proper action, but 'window-delete' as an alias will remain until more interesting changes require breaking configs.
2019-02-13fix missing includesokan-1/+2
2017-12-29Convert menu-exec-wm from an abritrary exec menu, into a config-based menu fromokan-29/+31
which one may configure (wm <name> <path_and_args>) (and choose) specific window managers to replace the running one. 'wm cwm cwm' is included by default. No objections and seems sensible to sthen.
2017-12-29As done for buttonrelease, work specific un-cycling and un-highlighting actionsokan-3/+10
into the keyrelease event, only performing what's actually needed for each; should result in much fewer events against keyreleases. No intended behaviour change. Additionally, like we do for group membership, grab the keyboard only when required for cycling.
2017-12-29Merge group_toggle_membership_leave into the buttonrelease event and only dookan-2/+2
border work for a group/ungroup action.
2017-12-29add helper function client_show to bring together like actions for unhide/raiseokan-5/+2
2017-12-19Use a variable to keep track of flags for menu_filter().okan-14/+22
2017-12-11Unconditionally show prompt on menus, regardless of invocation.okan-6/+4
2017-12-07Original idea from Dimitris Papastamos to move windows to corners a while ago;okan-1/+37
re-proposed by Julien Steinhauser with an updated diff. Apparently this was in the original calmnwm. However, expand the original idea and let clients 'snap' to edges instead, neatly allowing key bindings that snap to adjacent edges (i.e. corners) as well. No default bindings assigned.
2017-12-07give command and group menus their own match callbacksokan-6/+5
2017-12-07spacingokan-4/+3
2017-11-30Revert r1.109 (Switch to XWindowEvent() pulling out events that match the maskokan-3/+3
*and* window.) of mousefunc.c. When a client destroys itself while we are moving or resizing it, XWindowEvent() blocks. Found the hard way by Anton Lazarov, and Lea°hNeukirchen found the right bit to revert - thanks! Reverting since the reason to switch from XMaskEvent was unclear.
2017-07-14remove extra parenthesesokan-3/+3
2017-07-14Pull over the remaining re-implemented window move/resize functions and createokan-3/+140
a wrapper so that the key and mouse based move/resize callbacks can be unified. This has already been done with other window operations and menus.
2017-07-12rename one function, matching others, to help upcoming changeokan-2/+2
2017-07-10Replace fgetln(3) with POSIX getline(3); inspired by brynet and Ingo.okan-12/+11
feedback and ok brynet@
2017-05-09Alter callbacks to take a struct instead of a growing number of arguments;okan-51/+50
greatly simplifies upcoming work.
2017-05-01Clean up, unify and accurately calculate edge distance with client move/resizeokan-44/+22
actions, so as to not lose windows off the edge. inspired by diffs (and feedback) from Vadim Vygonets.
2017-01-05Ensure client stays inbound on key-based resize; based on logic existing inokan-1/+5
key-based client move; from Vadim Vygonets.
2016-12-06Add search_print_text(), a default callback for mi->print in menu_filter(). ↵okan-4/+4
While here, normalize the remaining search_print_* argument paramters.
2016-12-06Consistent use of menuq_add for ssh menu.okan-2/+2
2016-12-01Tame the number of 'exec' and 'path' search_match wrappers. No functionalokan-2/+2
change now, though more can likely go later, losing the (paritally complete or incomplete/broken) argument completion bits.
2016-12-01Switch ssh menu to search_match_text; like group/window/cmd menus, use only aokan-2/+2
substring match. The previous matching is only intended for the exec menus.
2016-12-01Change 'menu-window' to display all windows; then add 'menu-window-hidden' forokan-2/+3
the previous behaviour of 'menu-window'. 'menu-window' becomes the default binding; use 'bind-mouse "1" menu-window-hidden' to restore old behaviour for those who prefer. OK sthen@ (long long time ago on a different version)
2016-11-15Use an additional check with lstat(2) when d_type is unknown.okan-4/+11
from James McDonald via portable.
2016-11-15revert previous; upcoming changes will hopefully deal with these moreokan-23/+1
naturally.
2016-11-15Add a wrapper based upon xevent handlers around client move/resize for key andokan-1/+23
mouse bindings.
2016-10-24Make it clear these are flags.okan-7/+7
2016-10-24Sprinkle __func__ in appropriate error messages.okan-4/+4
2016-10-18Refactor callbacks to take a void * so as to not try and generalize intookan-167/+171
client_ctx in keypress and buttonpress event handlers; pass appropriate *ctx's based on context. While here, limit some globals, replace defines with appropriate variables and fix some naming.
2016-10-06Rename 2 kbfunc to match closer to what they dookan-3/+3
2016-10-06Add an argument to the callbacks to pass the xevent context, button orokan-36/+36
key press. This allows to remove a few hacks to duplicate functions only for behaviour changes; now differing behaviours are pushed down to the callback. Also will allow for previously unavailable actions to be bind-able down the road.
2016-10-03For both kb and mouse move, it is possible to grab a client and move itokan-2/+14
completely off the screen/region; instead, if the pointer is outside of the client bounds, warp the pointer to the closest edge before moving.
2016-10-03client_ptrwarp should not deal with unhiding or raising clients (non ptrokan-1/+3
requests); most callers do this already - deal with the few that do not. client_ptrwarp becomes a simple wrapper (setpos) but it will be expanded.
2016-09-22Continue merging kb and mouse functions: foldokan-8/+23
mousefunc_menu_{client,cmd,group} into the respective kbfunc_menu_{client,cmd,group} functions; simply pass a flag down from config denoting mouse action behaviour.
2015-11-17If a client does not set increment values, use 'moveamount' as a way tookan-8/+10
scale keyboard based resizes; extend kbfunc_amount(). Behaviour noted by, tested by, and ok sthen@
2015-11-12more client vs screen context differencesokan-5/+5
2015-11-12If a client sets hints, honor them for kb resize requests, just like weokan-5/+5
do for mouse based resize requests. Based on a patch from Vadim Vygonets.
2015-11-12Move kb pointer movement out of the kbfunc_client_moveresize since it'sokan-76/+93
got nothing to do with clients, thus doing flags work causes lots of waste and almost useless jumpy pointer movements; while here, split out move and resize since they share almost no code, just like mouse client move/resize; factor out amount and factor. Still wonder why this is here, but it works now.
2015-11-11Partial revert of replacing screen_area() with region_find(); until aokan-6/+7
fix for a regression is found; this bug has been around for a long time it seems, but this change exposed it. Likely need to track clients in to and out of regions.
2015-11-10Use position on root to figure out region.okan-4/+3
2015-11-10Start cleaning up name vs function differences; replace magic numbers.okan-18/+18
2015-11-09Extend region to include both view and work areas; switch tookan-6/+6
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.
2015-09-16On execwm, we should properly release resources before exec'ing into aokan-3/+4
new window manager; so allow CWM_EXEC_WM to assign new wm to wm_argv and pass through cwm_status (now EXECWM) so that x_teardown() gets called before exec'ing the new window manager. Removes the need for a separate x_restart() now, using new wm_argv; and consolidates errno for execvp.
2015-08-28Lost fix from r1.112; add comment.okan-2/+3
Reported (again!) by Peter Kane.
2015-08-27Move client cycle grab/ungrab into a more relevant place; while here,okan-9/+3
update comments about why we need to grab/ungrab the keyboard.
2015-08-21_NET_WM_STATE_STICKY implies only sticky at the group/desktop level, notokan-2/+2
position and size; based on discussion with a few.
2015-08-21Instead of special casing the 'term' and 'lock' commands, go back tookan-3/+7
keeping them hidden; showing them has apparently caused confusion/angst.
2015-07-12introduce 'groupsearch' for group menu search; matches on either groupokan-1/+26
number/shortcut and/or name.
2015-07-03revert previous; seems search_match_text() needs mi->text pre-populated.okan-2/+2
(only used in one place, application menu searching); re-visit later. broken application menu searching reported by Peter Kane.