| Age | Commit message (Collapse) | Author |
|
states appear. better handling of focusin's on clients that don't exist?
|
|
when a focusin comes for an invalid target, set that focus has wandered off, so
that when the focusout comes in afterwards we can react accordingly
|
|
destroy_notify which is really what it is, and is more consistant now that there are 2 notifies
|
|
most interesting is the change in focus_fallback, which means that it won't
call xsetinput focus in some cases, potentially reducing flicker and stuff.
also potentially producing bugs? heh.
the screen.c focus fallback code doesn't seem to need special cases anymore,
which is really good, if that is really the case.
move the focus_tried stuff out of event.c into focus.c, where it seems to
belong.
|
|
|
|
|
|
|
|
|
|
|
|
unmaps as we do so, so focus ends up going to nowhere
|
|
make _NET_RESTACK_WINDOW create a configurenotify, because it is supposed to be like configurerequest. so why not?
|
|
so just the one is shown
|
|
set the decor/functions after restoring all the stuff from session/per-app too
|
|
|
|
fix bottomif, topif, opposite.
fix debug output in event printing when there was no problem
|
|
|
|
no more cludge using actions to raise windows. when a window changes layer it
uses add_nonintrusive now so it won't cover the focused window. this way
fullscreen windows when they drop down, don't cover up the new focus target.
fix add_nonintrusive so that if the window is focused it gets added to the top
add back support for ConfigureRequest restacking, this time properly though,
using all the detail and sibling modes. but when windows use this to raise they
are using some old business and we're going to assume they actually want to
activate instead. this means firefox works nicely. yay.
ubuntu's firefox has been made to just stop raising entirely though. !
|
|
|
|
|
|
buttons count as clicking on the buttons
|
|
|
|
|
|
|
|
enter them.
|
|
|
|
|
|
|
|
instead which are the inverse. helper windows are utility/menu/toolbar windows.
|
|
|
|
enter/leave notify events.
dont change frame decor from button presses during an interactive grab or
while a menu is open
|
|
"client leader" which is in the WM_CLIENT_LEADER property. also they are all set when the window maps, and not to be changed thereafter.
|
|
the only thing i can think of tht would cause it. we will see..
|
|
improvements. with ksmserver we can save a few things before the clients go messing with stuff during the interactive phase.
|
|
|
|
|
|
|
|
renaming.
let you highlight disabled menu entries, they just aren't runable of course, and add the activedisabled theme element for these entries.
add the all desktops button picture to "All desktops" in the client menu
update the themes for the new element, and some changes to make things more readable-better contrast.
CLEARLOOKS-OLIVE is now DIFFERENT FROM THE 3.4 BRANCH SO DON'T RE-RUN THEMETOXML ON IT :( :(
yeah.. i think that is everything?
|
|
fix those stupid applications from moving accross the screen by the size of their decorations.
|
|
the client but not the frame for eg in iconify animation)
|
|
checking at runtime to make sure everything is in the atom.
|
|
mouse events..
|
|
frame logically and it will do everything except during animations the frame will show what it needs to for visual display.
|
|
perfectly now ?
one change in action.c may affect bindings... THIS COULD BREAK CURRENT CONFIG FILES. ya.
so, if you used a press binding and it moved the window, no enter event will be generated for that anymore because you are holding down the button when the window moves. if you don't like that then use a click binding instead.
1
|
|
|
|
focused, then don't restore focus how it was before showing the desktop.
|
|
let you do keyboard actions while move/resizing. yay. also you can click in windows at the same time..
|
|
don't handle focus fallbacks in that case until we know focus came back to our screen.
|
|
1) it can handle more user cases.
2) it can handle binding more modifier keys with their keysym names like Hyper and Super. W is a shortcut for Super, cuz the windows key is generally bound to it.
3) if you change your keymap bindings and reconfigure openbox it will learn your changes.
and i dunno.. its just nice and stuff now.. you can actually read it I think..
|
|
|
|
|