| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
from re-hiding on restart due to flag toggling (note that this is ripe
for re-vamping). Behavior only observed on restarts.
Problem found by, and initial patch from, Henri Kemppainen (thanks!),
though ever so slightly different one applied.
|
|
|
|
|
|
| |
and HOST_NAME_MAX+1, respectively.
ok doug@
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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).
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
prevent annoying behavior by only setting the cwm urgency flag if the client
is not active; diff from Thomas Adam.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
client_init and perform that X roundtrip only once.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
0x0 - don't allow this situation during mouse resize (check already in
place for kbd resize).
Reported by brynet@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
adjust callers. Needed for an upcoming feature.
|
|
|
|
| |
clients
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
from pwin
|
| |
|
| |
|
|
|
|
| |
events; based off a diff from Thomas Adam.
|
| |
|
| |
|
|
|
|
|
|
| |
the active flag but never redraw since it'll be in IconicState.
Behaviour reported by sthen@
|
|
|
|
| |
WM_NORMAL_HINTS.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
removing the border on maximized clients we need to redraw.
Also noticed by Tim van der Molen
|
| |
|
|
|
|
| |
wmprotocols, like rdesktop; focus needs to be re-visited
|