| Age | Commit message (Collapse) | Author |
|
Menus/Move/Resize
If the user has escape bound to more than one keycode then they can use any of
them to close a menu. This change applies to the hardcoded keys in openbox,
which are used for the menus and for move/resize, and maybe other places.
|
|
|
|
Previously, it would wait for a resize step before showing it, when resizing
windows with resize increments that were bigger than the moveresize threshold.
|
|
|
|
|
|
while resizing it - its not going to be responding to it anyways
|
|
|
|
values
|
|
|
|
|
|
|
|
|
|
from the edge (but it slows down after the first time)
|
|
little ugly.
|
|
ratios
|
|
|
|
them resist properly when resizing
|
|
direction being resized" which makes so much more sense and doesn't need all this conversion back and forth
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and from edge)
|
|
|
|
|
|
|
|
time around. eat enter events in client_configure when user is FALSE.
|
|
|
|
|
|
|
|
|
|
|
|
mode and drawcontents off
|
|
|
|
wonder if this will cause but reports. it still does for restacking though..
little cleanup in client.c, and remove client_configure macro which was now
redundant
|
|
|
|
add a confine option to grab_pointer to confine the pointer to the screen, and use that for moveresize
|
|
|
|
|
|
destroy_notify which is really what it is, and is more consistant now that there are 2 notifies
|
|
|
|
frame logically and it will do everything except during animations the frame will show what it needs to for visual display.
|