aboutsummaryrefslogtreecommitdiffstats
path: root/mousefunc.c (follow)
Commit message (Collapse)AuthorAgeLines
* 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.
* add support for mouse based group {,r}cycle; from Rodrigo Mosconi. notokan2013-07-08-1/+13
| | | | bound by default.
* move kbfunc and mousefunc closer togetherokan2013-07-08-7/+7
|
* move Cursors into conf.okan2013-06-17-3/+3
|
* - configure menuwin with the screen, then create the xft drawable usingokan2013-05-20-2/+2
| | | | | the menu window since that's the only place on which we draw - elminate the need to change the drawable on every font draw
* move the 2 small font helper functions to xutil.cokan2013-05-19-3/+4
|
* - let callers of font_draw figure out (and pass) the color instead of anokan2013-05-14-3/+3
| | | | | | 'active' flag. - use strlen() inside of font_draw; the only instance where it wasn't used happened to be ignored on a subsequent draw.
* get rid of cc->name in the resize box and make dimensions more readable.okan2013-05-02-13/+8
|
* only redraw the name/size box when the client resizes, not every timeokan2013-05-02-11/+6
| | | | there's movement; should slightly help with resize syncs.
* no need for font_{ascent,descent,height} wrappers; limit font_width tookan2013-05-02-7/+8
| | | | just requiring xftfont.
* plug memleak; always need to menuq_clear even when a selection is made.okan2013-04-08-5/+6
|
* consistencyokan2013-04-08-1/+3
|
* pass the screen workarea, as opposed to viewarea, allowing clientokan2013-01-02-3/+3
| | | | snapping to honor gap.
* re-work client_snapcalc() so it takes client and edge dimensions withokan2013-01-02-5/+5
| | | | | | snapdist; allows for simplier snap calculations. required for an upcoming diff for honoring gap.
* create and use menuq_clear() helper; from Tiago Cunhaokan2012-12-17-11/+4
|
* non-trivial menu drawing rewrite, moving to Xft and solving variousokan2012-12-17-3/+3
| | | | font/color drawing issues; from Alexander Polakov
* sortokan2012-11-09-2/+2
|
* get rid of the xfree() wrapper around free(); from Tiago Cunha.okan2012-11-07-3/+3
|
* extend client_resize so that it can know when to reset max flags andokan2012-09-09-3/+3
| | | | | | bwidth; this allows a client to be resized from a max state, which now gets treated like a non-max'd client. based on a diff that does part of this in a different way from Alexander Polakov.
* re-use geom struct in client_ctx (saved)geometry.okan2012-07-13-16/+16
|
* convert xmax/ymax uses to view geometry.okan2012-07-13-3/+3
|
* assign and use screen ctx where appropriate and consistently.okan2012-07-04-8/+6
|
* rename variable to reduce potential for name-space collision.okan2011-10-17-9/+9
| | | | bikesheding and ok oga@.
* split off window hints from geometry so we don't need to carry them allokan2011-09-03-3/+3
| | | | around when dealing with {,h,v}max. same idea from oga.
* We are inconsistent when it comes to function returns, so just go allokan2011-07-25-4/+4
| | | | | | the way with the cwm specific parts. ok oga@
* Clarify defines and make them not look like non-local ones; started by aokan2011-07-23-5/+5
| | | | | | small diff from Thomas Pfaff. ok oga@
powered by cgit and git | oriole.systems | how to verify signatures