| Commit message (Collapse) | Author | Lines |
|
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.
|
|
|
|
|
|
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@
|
|
for gathering Atoms.
|
|
|
|
|
|
*after* config parsing, we no longer need to split up display/screen
initialization, so collapse.
|
|
config options, add the keybinding GrabKey calls here
|
|
|
|
|
|
|
|
|
|
need to do this everytime; with Tiago Cunha
|
|
font/color drawing issues; from Alexander Polakov
|
|
|
|
|
|
|
|
existing argv; same idea with respect to argv saving as Alexander
Polakov. reload support was half-complete and is getting in the way.
agreed to by many
|
|
|
|
While testing for Xinerama during setup was done display-wide, each time
XineramaQueryScreens() is called either in start-up or due to an XRR
event, the library re-tests for the Xinerama extension anyway before
moving on; so the initial test is redundant and allows another global to
go away with one other change: always fill in sc->xinerama (and _no),
regardless of the success of malloc in XineramaQueryScreens(), and use
it to see if Xinerama dimensions exist when asked by client and/or menu
code.
|
|
move chuck to display init; allows some shuffling to occur limiting
screen_init_xinerama()'s scope while keeping order intact.
|
|
don't need to pass down the new values to screen_update_geometry(); so
just read the width/height values directly for both uses of
screen_update_geometry(). prep for further changes in this area.
|
|
dummy one to use instead; allows us to not have to wait for menu_init(),
so re-shuffle _NET_SUPPORTED slightly.
ok sthen@
|
|
|
|
from me.
ok oga@
|
|
the way with the cwm specific parts.
ok oga@
|
|
small diff from Thomas Pfaff.
ok oga@
|
|
sense and to be slightly less un-expected. from Alexander Polakov.
re-use 'normal' cursor now instead XC_hand1 for menu selection. i
really wish X had real docs and made sense.
ok on earlier diff with '?' removed (but it's back now) oga@
|
|
method that actually works. checking for icccm compliant wm's should
also be done first, but that's another diff (noted by oga).
ok oga@
|
|
|
|
This closes a race we were hitting often where stuff started right
before cwm may not get noticed and not have borders.
ok okan@. Prompted by something todd noticed.
|
|
- teach _NET_WORKAREA about gap.
ok oga@
|
|
are required.
encourged to go all the way by oga@
|
|
ok oga@
|
|
separate commits.
ok oga@
|
|
_NET_DESKTOP_GEOMETRY.
ok okan@
|
|
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@.
|
|
into screen_ctx and start passing screen_ctx around to in order get rid
of Curscreen; fixup per-screen config colors the same way.
diff mostly from oga@, with a bit harsher reaction to the state of screen_ctx.
"please commit" oga@
|
|
unchangable. the group code needs some cleaning up before this will be a
bit less hackish.
ok okan@
|
|
allows java to be happy, but additionally stops others from whinning
about a non-netwm complaint wm. more to come.
written a few times; this one includes a clever hack from oga@ to
populate _NET_SUPPORTED.
ok oga@
|
|
TAILQ_HEAD_INITIALIZER() and drop the function.
ok okan@
|
|
ok oga@
|
|
ok oga@
|
|
place anyway, this makes things a bit more consistent; from Thomas Pfaff
ok oga@
|
|
are far better ways to know.
"go for it" oga@
|
|
every other window manager since twm.
The event layer is very nice, very shiny, very flexible, and very much
underutilised. We don't need any of those shiny features so it's
probably better to earn ourselves 1k smaller text size instead.
ok todd@, okan@
|
|
using Xft(3), use it to select the font color as well instead of trying
to build one; properly allocate and free colors at-will, e.g. we now
have configurable colors.
feedback and ok's todd@ and oga@
|
|
requested by oga@
ok oga@ sometime ago
|
|
ok oga@
|