aboutsummaryrefslogtreecommitdiffstats
path: root/mousefunc.c (follow)
Commit message (Collapse)AuthorAgeLines
...
* 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@
* New option to raise a client via the mouse (unbound by default);okan2011-06-24-1/+7
| | | | | | | opposing action, lower, already exists and bound. Both keyboard mappings already exist. 'no opinion either way' oga@
* introduce a new config option to snap to the screen edge. 'snapdist'okan2011-06-24-1/+8
| | | | | | | | keyword taken from a diff from Sviatoslav Chagaev to do the same thing, but implemented in a completely way (based on some very old code from mk@). default set to 0, so no behavior change. ok oga@ (who would also like to take it further...)
* re-order sweep draw so that we map into the client window afterokan2011-06-24-4/+3
| | | | | | re-parenting; from Sviatoslav Chagaev. ok oga@
* struct XftFont already has height which we can use directly instead ofokan2011-06-24-5/+4
| | | | | | calculating ourselves, so do so. ok oga@
* remove left over XSync; ok oga@okan2011-05-13-7/+3
|
* tag and comment cleanup; ok oga@okan2011-05-11-4/+4
|
* introduce a new 'freeze' flag (CMS-f by default) which may be applied tookan2011-05-07-1/+7
| | | | | | | | | | | | | any window, after which all move/resize requests will be ignored, essentially freezing the window in place. there's a possibility to merge this with the 'ignore' concept, pending on how ignore+freeze should behave (really more ewmh stuff), but punting for now since ponies are on the line. requested and tested by thib at k2k11 with ponies, unicorns and rainbows. 'save the unicorns' todd@, ok oga@
* bump window resize back to 60hz. instead, we should not need to syncokan2011-05-05-6/+4
| | | | | | | every time we move/resize a window, so remove XSync in both mouse move and resize events. tested by Brynet as well. ok oga@
* revert the XSync timing change for client move only; first noticed byokan2011-03-23-3/+3
| | | | | | brynet. sure oga@
* reduce the number of times we sync during a window resize.okan2011-03-22-6/+5
| | | | ok oga@
* in MotionNotify geom.x, geom.y calculations take into account bwidth.martynas2010-12-14-3/+3
| | | | | fixes the annoying bug where windows would go +bwidth pixels right, +bwidth pixels down. ok okan@
* pull all non-X11 headers from calmwm.h and place them only where theyokan2009-12-15-1/+11
| | | | | | are required. encourged to go all the way by oga@
* merge the 2 common header files; specific includes to be pulled out asokan2009-12-15-2/+1
| | | | | | separate commits. ok oga@
* finish unfucking the screen_ctx handling.oga2009-12-10-6/+11
| | | | | | | | | | | | | remove screen_current() it was utterly bogus when nscreens > 1. pass a fake client_ctx in the case where there's no client and the kbfunc or mousefunc doesn't need a real one, it just contains the current screen, modify these functions so that they pass down the screen context to their callees. make groups per screen, it's the only way it makes sense in this regard. ok okan@.
powered by cgit and git | oriole.systems | how to verify signatures