aboutsummaryrefslogtreecommitdiffstats
path: root/kbfunc.c (follow)
Commit message (Collapse)AuthorAgeLines
* spacingokan2017-12-07-4/+3
|
* Revert r1.109 (Switch to XWindowEvent() pulling out events that match the maskokan2017-11-30-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.
* remove extra parenthesesokan2017-07-14-3/+3
|
* Pull over the remaining re-implemented window move/resize functions and createokan2017-07-14-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.
* rename one function, matching others, to help upcoming changeokan2017-07-12-2/+2
|
* Replace fgetln(3) with POSIX getline(3); inspired by brynet and Ingo.okan2017-07-10-12/+11
| | | | feedback and ok brynet@
* Alter callbacks to take a struct instead of a growing number of arguments;okan2017-05-09-51/+50
| | | | greatly simplifies upcoming work.
* Clean up, unify and accurately calculate edge distance with client move/resizeokan2017-05-01-44/+22
| | | | | | actions, so as to not lose windows off the edge. inspired by diffs (and feedback) from Vadim Vygonets.
* Ensure client stays inbound on key-based resize; based on logic existing inokan2017-01-05-1/+5
| | | | key-based client move; from Vadim Vygonets.
* Add search_print_text(), a default callback for mi->print in menu_filter(). ↵okan2016-12-06-4/+4
| | | | | | While here, normalize the remaining search_print_* argument paramters.
* Consistent use of menuq_add for ssh menu.okan2016-12-06-2/+2
|
* Tame the number of 'exec' and 'path' search_match wrappers. No functionalokan2016-12-01-2/+2
| | | | | change now, though more can likely go later, losing the (paritally complete or incomplete/broken) argument completion bits.
* Switch ssh menu to search_match_text; like group/window/cmd menus, use only aokan2016-12-01-2/+2
| | | | substring match. The previous matching is only intended for the exec menus.
* Change 'menu-window' to display all windows; then add 'menu-window-hidden' forokan2016-12-01-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)
* Use an additional check with lstat(2) when d_type is unknown.okan2016-11-15-4/+11
| | | | from James McDonald via portable.
* revert previous; upcoming changes will hopefully deal with these moreokan2016-11-15-23/+1
| | | | naturally.
* Add a wrapper based upon xevent handlers around client move/resize for key andokan2016-11-15-1/+23
| | | | mouse bindings.
* Make it clear these are flags.okan2016-10-24-7/+7
|
* Sprinkle __func__ in appropriate error messages.okan2016-10-24-4/+4
|
* Refactor callbacks to take a void * so as to not try and generalize intookan2016-10-18-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.
* Rename 2 kbfunc to match closer to what they dookan2016-10-06-3/+3
|
* Add an argument to the callbacks to pass the xevent context, button orokan2016-10-06-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.
* For both kb and mouse move, it is possible to grab a client and move itokan2016-10-03-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.
* client_ptrwarp should not deal with unhiding or raising clients (non ptrokan2016-10-03-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.
* Continue merging kb and mouse functions: foldokan2016-09-22-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.
* If a client does not set increment values, use 'moveamount' as a way tookan2015-11-17-8/+10
| | | | | | scale keyboard based resizes; extend kbfunc_amount(). Behaviour noted by, tested by, and ok sthen@
* more client vs screen context differencesokan2015-11-12-5/+5
|
* If a client sets hints, honor them for kb resize requests, just like weokan2015-11-12-5/+5
| | | | | | do for mouse based resize requests. Based on a patch from Vadim Vygonets.
* Move kb pointer movement out of the kbfunc_client_moveresize since it'sokan2015-11-12-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.
* Partial revert of replacing screen_area() with region_find(); until aokan2015-11-11-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.
* Use position on root to figure out region.okan2015-11-10-4/+3
|
* Start cleaning up name vs function differences; replace magic numbers.okan2015-11-10-18/+18
|
* Extend region to include both view and work areas; switch tookan2015-11-09-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.
* On execwm, we should properly release resources before exec'ing into aokan2015-09-16-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.
* Lost fix from r1.112; add comment.okan2015-08-28-2/+3
| | | | Reported (again!) by Peter Kane.
* Move client cycle grab/ungrab into a more relevant place; while here,okan2015-08-27-9/+3
| | | | update comments about why we need to grab/ungrab the keyboard.
* _NET_WM_STATE_STICKY implies only sticky at the group/desktop level, notokan2015-08-21-2/+2
| | | | position and size; based on discussion with a few.
* Instead of special casing the 'term' and 'lock' commands, go back tookan2015-08-21-3/+7
| | | | keeping them hidden; showing them has apparently caused confusion/angst.
* introduce 'groupsearch' for group menu search; matches on either groupokan2015-07-12-1/+26
| | | | number/shortcut and/or name.
* revert previous; seems search_match_text() needs mi->text pre-populated.okan2015-07-03-2/+2
| | | | | | (only used in one place, application menu searching); re-visit later. broken application menu searching reported by Peter Kane.
* no longer need to pass down format strings after introducing search_print_cmdokan2015-06-30-2/+2
|
* Introduce a callback for cmd menu printing, special-casing 'lock' andokan2015-06-30-2/+2
| | | | 'term'.
* Shuffle code in kbfunc_ssh so that a missing known_hosts file stillokan2015-06-29-8/+7
| | | | | | allows a (now blank) menu to appear, as opposed to nothing at all. Behavior reported by Alex Greif.
* Mechanical change from xinerama to region backed areas.okan2015-06-26-5/+5
|
* just populating the ctx is enough since the menu uses a callback and ignores ↵okan2015-06-08-2/+2
| | | | anything else
* merge kbd and mouse grouptoggleokan2015-05-21-4/+6
|
* Switch to limits.h; replace MAXPATHLEN and MAXHOSTNAMELEN with PATH_MAXokan2015-01-19-5/+6
| | | | | | 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-13/+13
|
* ewmh states _NET_WM_STATE_STICKY should not alter positionokan2014-09-17-2/+2
|