aboutsummaryrefslogtreecommitdiffstats
path: root/calmwm.h (unfollow)
Commit message (Collapse)AuthorLines
2014-01-22Somewhat streamline event loop/restart/quit handling; most notableokan-4/+8
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-3/+3
2014-01-20merge KBFLAG_NEEDCLIENT and MOUSEBIND_CTX_*; brings kbfunc and mousefuncokan-4/+3
bits even closer.
2014-01-20Use argument to pass down flags for mousefunc cyclegroup; removesokan-3/+1
rcyclegroup wrapper need - now similar to kbfunc.
2014-01-20constify and rename some confusing variables around cmdq.okan-7/+8
2014-01-20 - remove redundant range check for buttons in conf_bind_mouse.okan-3/+5
- make conf_bind_kbd return error on non-matches to match what conf_bind_mouse does. - rename some variables while here for clarity. - constify bind and cmd. from Tiago Cunha.
2014-01-20Add a function that adds an entry to a menuq, normalizing a common codeokan-1/+2
path; from Tiago Cunha.
2014-01-03use consistent typesokan-12/+12
2014-01-02bring mousefunc closer to kbfuncokan-13/+20
2014-01-02gc keycode in keybinding since we only deal with keysym nowokan-2/+1
2013-12-16Implement support for EWMH's _NET_WM_STATE_FULLSCREEN hint.okan-3/+8
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/+6
adjust callers. Needed for an upcoming feature.
2013-12-13Add support for XUrgency and matching _NET_WM_STATE_DEMANDS_ATTENTIONokan-2/+6
ewmh hint; urgencyborder is configurable. The urgency flag will stick, even while on a client in a non-viewable group, until the client receives focus (where the border is reset). Initial diff from Thomas Adam with some changes/enhancements from me.
2013-12-12ICCCM explicitly states that server time (CurrentTime) should *not* beokan-2/+3
used for focus events, but rather the timestamp of the generated event. Track the last event timestamp and send it down for a WM_TAKE_FOCUS ClientMessage. I suspect we should do this for clients that don't announce this Atom as well, though the raciness gets us into a bind. Solves focus order issue since WM_TAKE_FOCUS; fix verified by sthen@ ok sthen@
2013-12-11Add client wrapper for XWMHints to support XA_WM_HINTS in PropertyNotifyokan-1/+2
events; based off a diff from Thomas Adam.
2013-12-11Remove extra work and simplify client state handling.okan-4/+3
2013-12-11Stash Class and WM Hints in client_ctxokan-3/+3
2013-11-27like gap, make snapdist per screenokan-1/+2
2013-11-27Rewrite active/inactive client handling in client_setactive();okan-5/+3
client_leave() served no real purpose, likewise no reason to handle LeaveNotify events since an EnterNotify will process the next active client (and we don't have anything important to process anyway), so xev_handle_leavenotify() goes as well. Allows a simplification of client_mtf() and client_cycle_leave() for clarity. While here, unify a few client_current() checks. No intended behaviour change.
2013-11-12Alter the r1.35 of event.c race fix. Remove the forward looking eventokan-2/+2
queue check (removing the need for a server grab/ungrab) - if the client is going away, let it fall all the way through to a DestroyNotify event. There's no longer a need for us to manually destroy a client ourselves (removing yet another server grab/ungrab). Instead, when the UnmapNotify event is synthetic, simply set the state to Withdrawn (as per ICCCM), else Iconic (in our case 'hidden'). Verified with test case from the 2009 race which was the original reason for r1.35 of event.c.
2013-11-08stash WMProtocols in flagsokan-7/+3
2013-11-02The only reason we need to keep XSizeHints in our client_ctx is forokan-2/+2
flags, so just add one to hints; consolidates sizehints and shrinks. Additionally don't abuse PSize for XGetWMNormalHints() failures.
2013-11-01re-add support for WM_TAKE_FOCUS, and additionally this time only callokan-1/+2
XSetInputFocus() for clients that have the InputHint; latter fix discovered by Valery Masiutsin with a PoC patch - solves keyboard input focus loss for java apps.
2013-10-25A client_delete should behave differently depending on whether theokan-2/+2
triggering event was unmap (with pending destroy) log destroy; we only need to grab/ungrab the server lock, set WithdrawnState and XRemoveFromSaveSet clients coming from an unmap event - doing so for clients coming from destroy are already gone, hence we generate errors.
2013-10-20wrap key ungrab like btn ungrab, for it'll be used againokan-1/+2
2013-10-19Using xu_btn_ungrab() buttons during client_leave doesn't work (errorokan-2/+2
BadValue) when the modifier is already AnyModifier . Instead alter xu_btn_ungrab() to ungrab AnyButton/AnyModifier and call it only when a client is coming into focus in client_setactive(), instead of iterating over ignore mods - matches how we handle key grabs.
2013-10-03unify type; no changeokan-2/+2
2013-07-16max -> nitemsokan-4/+4
2013-07-15shuffle down protoypesokan-51/+48
2013-07-15simplify atom handling; allows us to limit to one round-trip to serverokan-8/+4
for gathering Atoms.
2013-07-09since the root and event window are the same in the case of a buttonokan-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.
2013-07-08add support for mouse based group {,r}cycle; from Rodrigo Mosconi. notokan-1/+5
bound by default.
2013-07-08move kbfunc and mousefunc closer togetherokan-10/+11
2013-07-08clarify kbd vs mouse functionsokan-3/+3
2013-06-17move Cursors into conf.okan-7/+12
2013-06-10move synthetic responses and have client_msg only work with WM_PROTOCOLS,okan-3/+3
since that's all ClientMessageEvent is for anyway.
2013-05-27fix type in a ClientMessage (xu_sendmsg).okan-2/+2
2013-05-23alter conf_grab(_kbd) to first ungrab AnyKey/AnyModifier, then proceedokan-5/+3
to grab keys in keybindingq. we don't need to ungrab/grab on every addition to the queue, just once with a complete keybindingq; simplify grabbing keys per screen (during init) and during a MappingNotify. while here, change conf_grab_{kbd,mouse} to require only a Window.
2013-05-22move validation of pointer Button into conf_mousebind so we checkokan-2/+2
validity during the parse phase and not bother adding it to the queue, instead of each time a client needs to grab (when it's too late); furthermore, make this a config error, stop parsing and load the default config.
2013-05-21handle _NET_WM_STATE ClientMessage; from Alexander Polakov.okan-1/+8
2013-05-20add support for _NET_WM_STATE_MAXIMIZED_{HORZ,VERT}; from Alexander Polakov.okan-1/+8
while I'm unsure of the final look of _NET_WM_STATE, there's no reason to delay this support.
2013-05-20- configure menuwin with the screen, then create the xft drawable usingokan-3/+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
2013-05-19move the 2 small font helper functions to xutil.cokan-5/+4
2013-05-19move the rest of xft init into screen_conf, since most of it is based onokan-2/+1
config parameters.
2013-05-19- switch border colors to Xftokan-20/+11
- merge border/menu color structures/functions since they now both use Xft - switch xu_xorcolor to operating on XftColor instead of just XRenderColor (basically adding pixel) - if color name allocation fails, revert back to default (this, along with font validation should occur during config parse, but we don't have screens setup yet - likely to change at some point)
2013-05-19add support for _NET_CLOSE_WINDOWokan-1/+2
2013-05-19treat WM_CHANGE_STATE like other atomsokan-1/+2
2013-05-19use XGetWMProtocols and simplify WM_PROTOCOL handlingokan-4/+7
2013-05-14- let callers of font_draw figure out (and pass) the color instead of anokan-2/+2
'active' flag. - use strlen() inside of font_draw; the only instance where it wasn't used happened to be ignored on a subsequent draw.
2013-05-11new -> initokan-2/+2
powered by cgit and git | oriole.systems | how to verify signatures