aboutsummaryrefslogtreecommitdiffstats
path: root/kbfunc.c (unfollow)
Commit message (Collapse)AuthorLines
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.
2015-06-30no longer need to pass down format strings after introducing search_print_cmdokan-2/+2
2015-06-30Introduce a callback for cmd menu printing, special-casing 'lock' andokan-2/+2
'term'.
2015-06-29Shuffle code in kbfunc_ssh so that a missing known_hosts file stillokan-8/+7
allows a (now blank) menu to appear, as opposed to nothing at all. Behavior reported by Alex Greif.
2015-06-26Mechanical change from xinerama to region backed areas.okan-5/+5
2015-06-08just populating the ctx is enough since the menu uses a callback and ignores ↵okan-2/+2
anything else
2015-05-21merge kbd and mouse grouptoggleokan-4/+6
2015-01-19Switch to limits.h; replace MAXPATHLEN and MAXHOSTNAMELEN with PATH_MAXokan-5/+6
and HOST_NAME_MAX+1, respectively. ok doug@
2014-09-27these have nothing to do with 'sticky', but rather group membership; rename.okan-2/+2
2014-09-17these client actions are just toggles; less confusing with better namesokan-13/+13
2014-09-17ewmh states _NET_WM_STATE_STICKY should not alter positionokan-2/+2
2014-09-11Remove incorrect cast in kbfunc_exec. In kbfunc_ssh, reverse logic onokan-5/+5
truncation check so it's obvious.
2014-09-08Remove duplicate client queue (mruq); instead, remove and take theokan-2/+2
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-06Few style nits; extend 'path' to MAXPATHLEN.okan-11/+14
2014-09-06Move termpath and lockpath into cmdq; side effect is that 'lock' andokan-4/+17
'term' now show up in the application menu.
2014-09-01add explicit paran and drop some empty lines bringing like functions closerokan-2/+1
2014-08-25Implement _NET_WM_STATE_STICKY, bound to CM-s by default; allows anyokan-1/+7
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-01-30Move cwm_status around to avoid header fu, and remove extraneous signalokan-1/+3
header from xevents.c; noticed by Christian Neukirchen.
2014-01-29Minimize trivial differences between a few kb and mb functions.okan-2/+2
2014-01-23If no title is supplied, term uses only the basename for its title.okan-3/+3
This is useless when searching for windows launched via the ssh command menu; supply a more useful title: '[ssh] <hostname>'. Idea from todd@, ok todd@
2014-01-22zap whitespaceokan-26/+26
2014-01-22Somewhat streamline event loop/restart/quit handling; most notableokan-13/+3
change allows a restart to trigger proper teardown first, even though teardown is not (yet) complete. After some discussion with oga@nicotinebsd.org regarding a more complicated version/idea.
2014-01-21Sprinkle a few more const; from Tiago Cunha.okan-2/+3
2014-01-20Save the ptr position before lowering via kbd, so as to be able to cycleokan-1/+2
back with the pointer in the right place; matches behaviour when lowering via the mouse function.
2014-01-20constify and rename some confusing variables around cmdq.okan-3/+3
2014-01-20Add a function that adds an entry to a menuq, normalizing a common codeokan-24/+8
path; from Tiago Cunha.
2014-01-03use consistent typesokan-2/+2
2013-12-16Implement support for EWMH's _NET_WM_STATE_FULLSCREEN hint.okan-1/+7
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-2/+2
adjust callers. Needed for an upcoming feature.
2013-12-13Instead of using work area, use the Xinerama area for snap calculations;okan-3/+7
based on a patch from Thomas Adam with appropriate adjustments for gap.
2013-12-12Make sure we really take work area gap into account with snap calculations;okan-3/+3
from Dominik Honnef via Christian Neukirchen.
2013-11-27like gap, make snapdist per screenokan-3/+3