| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Just "do the right thing" based on if you are connected to a session manager
or not.
|
|
Conflicts:
openbox/popup.c
|
|
them "undecorated" with the keepborder config option on.
This fixes what commit 85f39cd27e7ea0eec8bc78f6139092b44fda2dad fixed for the
fullscreen window case, but also fixes bug #4344.
|
|
struts with multiple monitors.
|
|
while it is going to be shown later by a delay.
|
|
|
|
|
|
|
|
Just kidding. This doesn't revert d81d54c7a977a034199f24fc8fa7433e634aaf91 but
it redoes the work that patch reverted in a better, less intrusive, way.
|
|
This reverts commit fd2f617be7ff57fcb187daa737f66d243544c8cd.
This reverts commit a47d0a53652a96ca1df96fc9268757df1431ae55.
This reverts commit a1908e076736e1a618bd305c5963dbfecaa30497.
This reverts commit dc2e6f6bf7143a56de360a393b33906735e63625.
This reverts commit 985e7dadf9a3ebf4bd265d955c3198e96405e5d2.
This reverts commit db781556d63d1a50bd1b1b4b6b5423ef703bf2c7.
This reverts commit feec8f663f0a11546c2da87575fecc8a88d97ca1.
|
|
Add asserts to default: in switch statements
Store pointed to variables locally so it knows they don't change
Remove some dead assignments
Mark ob_exit_with_error as noreturn
Use "%s", msg instead of just msg to printf style functions
Use the c_pfocus variable
|
|
|
|
|
|
|
|
Google's chrome does this when you toggle window decorations.
Based on patch in #4250 by Daniel Erat.
|
|
|
|
Conflicts:
openbox/actions/desktop.c
openbox/client.c
openbox/event.c
openbox/extensions.c
openbox/popup.c
openbox/screen.c
parser/parse.c
|
|
It doesn't look good in some places, e.g. WnckTasklist (gnome-panel)
[ Also update translations -- Mikael ]
|
|
|
|
Currently you can't mark anything that comes after the __ with _ to make
that a shortcut.
|
|
We check that xinerama is active already, but someone got a NULL here.
|
|
|
|
According to the WM Specification, the left, top, right, and bottom
fields are to be declared relative to the overall X screen dimensions,
not the monitor dimensions.
The example given in the spec (v1.3 or 1.4draft2) is: "Another example
is a panel on a screen using the Xinerama extension. Assume that the
set up uses two monitors, one running at 1280x1024 and the other to the
right running at 1024x768, with the top edge of the two physical displays
aligned. If the panel wants to fill the entire bottom edge of the smaller
display with a panel 50 pixels tall, it should set a bottom strut of 306,
with bottom_start_x of 1280, and bottom_end_x of 2303. Note that the strut
is relative to the screen edge, and not the edge of the xinerama monitor."
In my case, I have a 1680x1050 monitor to the left of a 1920x1200 monitor
aligned at the top. I then have a gnome-panel along the bottom edge of
the 1680x1050 monitor with a height of 24 pixels.
xprop reports the following partial strut: _NET_WM_STRUT_PARTIAL(CARDINAL)
= 0, 0, 0, 175, 0, 0, 0, 0, 0, 0, 0, 1679 which is correct according to
the spec. Gnome-panel is reserving the 150 pixels along the bottom that
aren't visible on the screen plus the 25 it requests for itself.
However, maximizing a window on this monitor leaves a gap of exactly 150
pixels between the bottom edge of the maximized window and the top edge
of the panel.
Also, when the 1680x1050 monitor is the primary monitor (id=1) then the
_NET_WORKAREA property on the root window is also off by 150px for the
same reason.
This patch fixes the two issues I mentioned for exterior monitor edges.
It doesn't attempt to account for "interior" monitor edges (i.e. a 'left'
strut on monitor A when monitor B is directly to the left of monitor A)
because it's not possible to do so with the current strut specification
(see http://mail.gnome.org/archives/wm-spec-list/2004-March/msg00004.html
for a discussion on this limitation)
This could be avoided by having the partial strut atom contain a xinerama
screen ID that the strut applies to, but unfortunately the discussion
all those years ago never got anywhere.
[ quoted from bug #3792 ]
|
|
|
|
This should be a satisfactory fix for #3694 I hope.
|
|
Only the chroot popup uses delayed mapping so this is just a latent bug.
|
|
One of the Debian users asked if it's possible to send a window to other
monitor when using xinerama, especially useful of you have 2 monitors and want
to toggle a window to the other one. I wrote a patch that implements next and
prev to also make that work for 3 or more workspaces.
|
|
the window to become unmanaged
|
|
|
|
This caused problems for placing windows with decor turned off, the
placement code thought they had it on.
|
|
Some compilers, like sun studio and clang don't support them.
|
|
|
|
Conflicts:
openbox/config.c
|
|
A couple of things were wrong, the parser added 1 to the value despite
expecting the user to give values in the range of 1 to
screen_num_monitors, rc.xml documented the values to start from 0 and
finally the monitor value wasn't copied over at all when matching the
client.
|
|
Conflicts:
openbox/event.c
openbox/frame.c
|
|
Many composite apps use this to pass through clicks where they are transparent.
|
|
|
|
avoid overriding bar=no
|
|
Using format specifiers without arguments in printf is still bad.
openbox/debug.c:105:18: warning: format string is not a string literal (potentially insecure)
fprintf(out, log_domain);
^~~~~~~~~~
openbox/debug.c:107:18: warning: format string is not a string literal (potentially insecure)
fprintf(out, level);
^~~~~
openbox/debug.c:109:18: warning: format string is not a string literal (potentially insecure)
fprintf(out, message);
^~~~~~~
|
|
Conflicts:
openbox/event.c
|
|
This poses a small problem. We currently let translators reorder this
string, but ngettext only takes one numeric argument. This means that you
can either get correct pluralization or the order you want, but not both.
I fixed up the languages I understand at a very basic level, but the
rest will need translator assistance.
|
|
openbox/client.c:269:10: warning: incompatible pointer types passing 'gint *', expected 'guint32 *'
if (!OBT_PROP_GET32(self->window, NET_WM_USER_TIME, CARDINAL, &user_time))
^~~~~~~~~~~~~~
|
|
didn't come from the user.
Instead, just activate the flashy thinger.
|
|
|
|
|
|
|
|
|
|
Conflicts:
openbox/client.c
openbox/prop.c
openbox/prop.h
|
|
|
