aboutsummaryrefslogtreecommitdiffstats
path: root/mousefunc.c (follow)
Commit message (Collapse)AuthorAgeLines
* Continue merging kb and mouse functions: foldokan2016-09-22-78/+1
| | | | | | 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.
* Limit mouse resize to hints within the client; matches kbd resizeokan2016-09-13-8/+3
| | | | behaviour.
* Inline the only use of mousefunc_sweep_calc.okan2015-11-17-17/+8
|
* 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-3/+2
|
* Start cleaning up name vs function differences; replace magic numbers.okan2015-11-10-2/+2
|
* 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.
* _NET_WM_STATE_STICKY implies only sticky at the group/desktop level, notokan2015-08-21-3/+3
| | | | position and size; based on discussion with a few.
* Instead of special casing the 'term' and 'lock' commands, go back tookan2015-08-21-2/+6
| | | | keeping them hidden; showing them has apparently caused confusion/angst.
* introduce 'groupsearch' for group menu search; matches on either groupokan2015-07-12-5/+3
| | | | number/shortcut and/or name.
* styleokan2015-07-01-4/+4
|
* 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'.
* Mechanical change from xinerama to region backed areas.okan2015-06-26-5/+5
|
* switch to search_print_client() as the print callback since it will now ↵okan2015-06-08-8/+3
| | | | display labels as well
* stash window dimensionsokan2015-06-08-4/+2
|
* even if the menuq is empty, at least show an empty menu instead of justokan2015-06-07-7/+1
| | | | bailing making it look like the binding isn't working.
* add a flag to indicate a menu list instead of overloading 'prompt'okan2015-06-05-4/+4
|
* merge kbd and mouse grouptoggleokan2015-05-21-7/+1
|
* 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
|
* Move motion time check to the top of each MotionNotify block (andokan2014-09-18-17/+16
| | | | | | eliminate from ButtonRelease); further limits the amount of work done outside the threshold, notably mousefunc_sweep_calc, screen_find_xinerama and client_snapcalc.
* ewmh states _NET_WM_STATE_STICKY should not alter positionokan2014-09-17-3/+3
|
* Use a similarly named check as sticky for hidden check in a group.okan2014-09-17-3/+3
|
* Introduce a check to see if a group holds only 'sticky' clients and useokan2014-09-17-2/+2
| | | | | | | | this check to decide if a group is virtually empty. Rationale: if a group contains *only* 'sticky' clients, it should be skipped while cycling through groups. Apply similar logic to the group menu. Based on an idea from phessler@, who also tested another version.
* name the group client queue appropriately, like other queuesokan2014-09-08-2/+2
|
* Remove duplicate client queue (mruq); instead, remove and take theokan2014-09-08-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).
* Now that a group knows its screen, only pass down the group_ctx.okan2014-09-08-2/+2
|
* Rework group names: stash the group name inside the group_ctx as opposedokan2014-09-06-2/+2
| | | | | | to having to manage an array outside in screen_ctx for group names and shortcuts. Simplifies (and moves bits for) reading, and constructing data for, EWMH's _NET_DESKTOP_NAMES.
* bring menu bits closer togetherokan2014-09-02-4/+3
|
* add explicit paran and drop some empty lines bringing like functions closerokan2014-09-01-6/+3
|
* Merge group_menu into mousefunc_menu_group.okan2014-09-01-2/+26
|
* Fix nogroup regression, where nogroup became an actual group - theokan2014-08-22-2/+3
| | | | | | | | | | symantics between cwm groups and ewmh got in the way. Ensure a client that wants to be in nogroup stays in nogroup (thus stays in view), even when (re)reading NET_WM_DESKTOP. Paritially reverts patchset 644 (2014-02-07 13:09 PST) which deals with a NULL cc->group. All to be revisited when NET_WM_STATE_STICKY hits cwm. Reported by many; testing and ok phessler.
* Purely mechanical; unify 'num', 'no' and 'shortcut'.okan2014-08-20-3/+2
|
* all mapped clients now should have a group, so simplify some casesokan2014-02-07-2/+2
|
* Remove duplicate mouse functions and instead use the kbfunc ones. Nookan2014-01-30-26/+1
| | | | | user visable changes at this point, but they'll merge at an appropriate time.
* Minimize trivial differences between a few kb and mb functions.okan2014-01-29-8/+7
|
* Use argument to pass down flags for mousefunc cyclegroup; removesokan2014-01-20-8/+2
| | | | rcyclegroup wrapper need - now similar to kbfunc.
* constify and rename some confusing variables around cmdq.okan2014-01-20-3/+3
|
* Add a function that adds an entry to a menuq, normalizing a common codeokan2014-01-20-11/+4
| | | | path; from Tiago Cunha.
* bring mousefunc closer to kbfuncokan2014-01-02-12/+12
|
* Teach screen_find_xinerama() to apply gap only when told to do so;okan2013-12-13-2/+2
| | | | adjust callers. Needed for an upcoming feature.
* Instead of using work area, use the Xinerama area for snap calculations;okan2013-12-13-3/+7
| | | | based on a patch from Thomas Adam with appropriate adjustments for gap.
* Make sure we really take work area gap into account with snap calculations;okan2013-12-12-3/+3
| | | | from Dominik Honnef via Christian Neukirchen.
* If not using sticky mode (the default), clients aren't automagicallyokan2013-12-08-3/+3
| | | | | assigned a group, thus cc->group will be NULL - fix the client group shortcut in menu lists; crash reported by Christian Neukirchen.
* Prepend the group shortcut in the client search menu; from Thomas Adam.okan2013-12-02-2/+3
| | | | Likewise, prepend shortcut in unhide menu.
* like gap, make snapdist per screenokan2013-11-27-3/+3
|
* simplify/unfoldokan2013-11-27-7/+5
|
* I believe we redraw the border in too many cases; likely a leftover fromokan2013-10-19-9/+3
| | | | | | | | | 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!
* since the root and event window are the same in the case of a buttonokan2013-07-09-2/+2
| | | | | | | event on the screen's root window, there's no need to pass down the entire XButtonEvent event, at least to group_menu(), the only callback which takes an argument at this point; instead use the already populated screen.
powered by cgit and git | oriole.systems | how to verify signatures