| Commit message (Collapse) | Author | Age | Lines |
... | |
|
|
|
| |
client_hmax); from Jan Stary
|
| |
|
| |
|
|
|
|
|
|
| |
snapdist; allows for simplier snap calculations.
required for an upcoming diff for honoring gap.
|
|
|
|
| |
XineramaScreenInfo; simplifies goop around the callers.
|
| |
|
| |
|
|
|
|
| |
a malloc'd variable everytime; from Tiago Cunha
|
|
|
|
|
|
| |
note that a re-exec of cwm will not rewrite the group number atom of
*existing* clients, so they will remain off-by-one until each client has
its atom updated, or of course a restart of X.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
when calculating screen dimensions.
|
|
|
|
| |
moves closer to logic in menu code.
|
| |
|
| |
|
|
|
|
|
|
|
| |
window manager didn't know if a client supported CLIENT_PROTO_DELETE and
thus used a hammer, XKillClient.
behaviour reported by Tim van der Molen.
|
|
|
|
| |
separation between cwm and ewmh. seen by a few.
|
|
|
|
|
|
| |
Alexander Polakov.
ok sthen@
|
|
|
|
|
| |
persistence; based on a diff from Alexander Polakov, in preparation for
looping through other potential cycling modifiers.
|
| |
|
|
|
|
|
|
|
| |
the group of the main application window; based on a diff from Alexander
Polakov with CLIENT_IGNORE flag suggestion from oga@.
ok oga@
|
| |
|
|
|
|
|
|
|
|
|
|
| |
i.e. horiz-max + vertmax = full maximisation. full - horiz = vertmax.
etc.
Martynas wrote something like this once, so I did okan, this version
seems to finally deal with the corner cases.
ok okan@.
|
|
|
|
| |
around when dealing with {,h,v}max. same idea from oga.
|
|
|
|
|
|
|
| |
group as the active client (as opposed to all unhidden clients); from
Alexander Polakov, with a tiny tweak requested by oga.
ok oga@
|
| |
|
|
|
|
|
|
|
|
| |
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...)
|
|
|
|
|
|
|
| |
as a bonus, flipping between various combinations of vmax+hmax provides
a more predictable behavior.
commitski oga@
|
|
|
|
| |
ok oga@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
|
| |
coordinates; allows moving a client and not restoring the maximized axis
coordinates.
picked from a larger martynas diff from ages ago.
ok oga@
|
|
|
|
|
|
|
| |
(noticed by Tim Peniket), since we don't ever do anything with cliarg,
remove the hunk and cliarg completely.
ok oga@
|
|
|
|
|
|
| |
reminded by a similiar diff from Thomas Pfaff.
ok oga@
|
|
|
|
|
|
|
|
|
|
|
| |
that if it is not already inbounds, put it in the default location,
which happens to be inbounds.
behavior noticed by Thomas Pfaff while maximizing and un-maximizing a
window, leaving the pointer behind and causing client_cycle() to be a
bit lost.
ok oga@
|
|
|
|
|
|
|
|
| |
use the appropriate netwm Atom first, as well as deal with utf8.
slightly different incarnation tested by sthen@ and ajacoutot@ - thanks!
ok oga@
|
|
|
|
| |
ok oga@
|
|
|
|
|
|
| |
Makes XMMS windows appear as expected.
ok okan, oga
|
|
|
|
|
|
| |
- teach _NET_WORKAREA about gap.
ok oga@
|
|
|
|
|
|
| |
are required.
encourged to go all the way by oga@
|
|
|
|
| |
ok oga@
|
|
|
|
|
|
| |
separate commits.
ok oga@
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@.
|
|
|
|
|
|
|
|
| |
the x property api doesn't let you remove one entry from an X property
array, so client_remove is kinda expensive, but there's no real way
around that..
ok okan@
|
|
|
|
|
|
|
| |
supported, the client message to change this will be supported when all
informational hints are working.
ok okan@
|