aboutsummaryrefslogtreecommitdiffstats
path: root/calmwm.h (follow)
Commit message (Collapse)AuthorAgeLines
...
* Implement EWMH _NET_WM_STATE_HIDDEN.okan2014-09-17-2/+4
|
* 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.
* fold in 'active' into 'flags'okan2014-09-10-2/+2
|
* 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-7/+4
| | | | | | 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-3/+3
|
* Add screen_ctx to group_ctx, and populate on init.okan2014-09-07-1/+2
|
* screen_fromroot -> screen_findokan2014-09-07-2/+2
|
* Get rid of a redundant array of groups per screen; we already have aokan2014-09-07-2/+1
| | | | link to the group queue for each screen.
* Move termpath and lockpath into cmdq; side effect is that 'lock' andokan2014-09-06-3/+1
| | | | 'term' now show up in the application menu.
* Rework group names: stash the group name inside the group_ctx as opposedokan2014-09-06-3/+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.
* Merge group_menu into mousefunc_menu_group.okan2014-09-01-2/+4
|
* Since the flatting out of sc->group_names is only for settingokan2014-08-25-3/+2
| | | | | NET_DESKTOP_NAMES, merge the helper into xu_ewmh_net_desktop_names, where we actually set the property.
* Implement _NET_WM_STATE_STICKY, bound to CM-s by default; allows anyokan2014-08-25-2/+6
| | | | | | | 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.
* gc->hidden has never consistently kept track of a group's state;okan2014-08-24-3/+1
| | | | | | | | | | group_show() and group_hide() are not the only ways a group can change state - if all clients in a group are either hidden or unhidden, then that group's state should change, as well as the various EWMH ways. Instead of trying to keep track in a wide variety of places, simply query the clients in a group before needing to take action based on the group's state. Solves long standing confusion of when a group is hidden or not.
* Purely mechanical; unify 'num', 'no' and 'shortcut'.okan2014-08-20-2/+2
|
* Pull highstack from group_ctx (and useless calculations of); in the oneokan2014-08-19-2/+1
| | | | | place that we use highstack, replace that usage with a local variable (for now until stacking is done properly).
* Get rid of nhidden in group_ctx; it actually never reported correctlyokan2014-08-18-2/+1
| | | | | | | since nhidden wasn't incremented nor decremeted in all the right places, thus confusing matters. We don't need to carry a count around, so just use a local variable in the one place we need one to supply XRestackWindows().
* Make sure we cycle through existing client's group membership and setokan2014-02-08-1/+2
| | | | | the hidden state on the group; important to know group hidden state after a re-exec or restart of cwm (as easily seen in group menu).
* Introduce a region queue and replace screen's XineramaScreenInfo; weokan2014-02-03-3/+9
| | | | | still use Xinerama to populate the regions per screen, but will switch at a more appropriate time.
* Move redundant bits from screen_init (while dealing with existingokan2014-02-03-2/+2
| | | | | | clients) directly into client_init, performing the X roundtrip only once. With the previous change in maprequest, this moves decision making into one place for creating new clients.
* No need to store screen colormap and visual; rather just use the Xokan2014-02-02-3/+1
| | | | macros in the one place they are needed.
* The menu already limits entries with MENU_MAXENTRY, so don't botherokan2014-02-02-5/+4
| | | | holding a command name limit as well.
* Switch ignoreq to winname struct since it's basically the same thing;okan2014-01-30-10/+4
| | | | removes limit on name matching.
* Move cwm_status around to avoid header fu, and remove extraneous signalokan2014-01-30-2/+1
| | | | header from xevents.c; noticed by Christian Neukirchen.
* Remove duplicate mouse functions and instead use the kbfunc ones. Nookan2014-01-30-9/+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-2/+2
|
* Merge keybinding and mousebinding queues into using the same mergedokan2014-01-29-16/+12
| | | | | struct, binding; they were essentially the same accept for what was 'pressed', keysym or button.
* Check command name/path for truncation and provide user feedback duringokan2014-01-29-2/+2
| | | | | | config parse (and use conf_cmd_add to populate defaults); based on a discussion with Tiago Cunha. While this looks ugly, there are likely some other changes here to come.
* Check ignore windowname for truncation and provide user feedback duringokan2014-01-28-2/+2
| | | | config parse; based on a discussion with Tiago Cunha.
* Somewhat streamline event loop/restart/quit handling; most notableokan2014-01-22-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.
* Sprinkle a few more const; from Tiago Cunha.okan2014-01-21-3/+3
|
* merge KBFLAG_NEEDCLIENT and MOUSEBIND_CTX_*; brings kbfunc and mousefuncokan2014-01-20-4/+3
| | | | bits even closer.
* Use argument to pass down flags for mousefunc cyclegroup; removesokan2014-01-20-3/+1
| | | | rcyclegroup wrapper need - now similar to kbfunc.
* constify and rename some confusing variables around cmdq.okan2014-01-20-7/+8
|
* - remove redundant range check for buttons in conf_bind_mouse.okan2014-01-20-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.
* Add a function that adds an entry to a menuq, normalizing a common codeokan2014-01-20-1/+2
| | | | path; from Tiago Cunha.
* use consistent typesokan2014-01-03-12/+12
|
* bring mousefunc closer to kbfuncokan2014-01-02-13/+20
|
* gc keycode in keybinding since we only deal with keysym nowokan2014-01-02-2/+1
|
* Implement support for EWMH's _NET_WM_STATE_FULLSCREEN hint.okan2013-12-16-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@
* Teach screen_find_xinerama() to apply gap only when told to do so;okan2013-12-13-2/+6
| | | | adjust callers. Needed for an upcoming feature.
* Add support for XUrgency and matching _NET_WM_STATE_DEMANDS_ATTENTIONokan2013-12-13-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.
* ICCCM explicitly states that server time (CurrentTime) should *not* beokan2013-12-12-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@
* Add client wrapper for XWMHints to support XA_WM_HINTS in PropertyNotifyokan2013-12-11-1/+2
| | | | events; based off a diff from Thomas Adam.
* Remove extra work and simplify client state handling.okan2013-12-11-4/+3
|
* Stash Class and WM Hints in client_ctxokan2013-12-11-3/+3
|
* like gap, make snapdist per screenokan2013-11-27-1/+2
|
* Rewrite active/inactive client handling in client_setactive();okan2013-11-27-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.
* Alter the r1.35 of event.c race fix. Remove the forward looking eventokan2013-11-12-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.
powered by cgit and git | oriole.systems | how to verify signatures