| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
While the configured layout is taken into account for positioning
the buttons, the mapping from button function states to button
position states just assumed the default button layout in LTR
locales.
Do a proper mapping depending on the actual layout instead.
https://bugzilla.gnome.org/show_bug.cgi?id=638700
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
From http://live.gnome.org/Design/SystemSettings/Keyboard
https://bugzilla.gnome.org/show_bug.cgi?id=641282
|
| |
|
| |
|
|
|
|
|
| |
which was breaking the build. Closes bug 640719. Thanks to Luca Ferretti
for reporting this.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts most of commit abbd057eb967e6ab462ffe305f41b2b04d417b25;
- It's fine to call meta_session_shutdown() after the display
is closed, since it's talking over the ICE connection
- We should not call warn_about_lame_clients_and_finish_interact()
unless we are interacting with the window manager in a session
save.
However, the part of abbd057 that fixed accessing freed memory was
fixing a real problem; this patches does the same thing in a simpler
way by fixing an obvious type in meta_display_close() where it was
NULL'ing out the local variable 'display' rather than the global
variable 'the_display' and adding keeping the check in meta_finalize()
that was added in abbd057.
The order of calling meta_session_shutdown() and
calling meta_display_close() is reverted back to the old order to
make it clear that it's OK if the display way already closed previously.
|
|
|
|
|
|
|
|
| |
In order to replace calls to deprecated GDK code, yet-unreleased
GTK+ 2.22 is required. Add some basic compatibility code to allow
building mutter with GTK+ 2.20.
https://bugzilla.gnome.org/show_bug.cgi?id=572332
|
|
|
|
|
|
|
| |
Commit 15f273e7 uses API introduced in the current cycle, but I
forgot to bump the version requirements.
https://bugzilla.gnome.org/show_bug.cgi?id=572332
|
|
|
|
|
|
|
|
|
|
|
| |
We currently allow XRaiseWindow when the same application (defined
by the window group) is focused, but the kind of old applications
that XRaiseWindow are frequently not setting the window group.
Expand the check to allow the same X client (defined by the looking
at client ID) to raise windows above the focus window.
https://bugzilla.gnome.org/show_bug.cgi?id=567528
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
A test case for this patch is available at
https://view.svn.sourceforge.net/svnroot/view/trunk/wm-test-suite/
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes two issues on Solaris:
1) It is necessary on Solaris to run PKG_CHECK on gthread-2.0 and add
glib/gthread to METACITY_LIBS in order for metacity to compile. This is
because Solaris doesn't allow implicit linking.
2) src/compositor/compositor-xrender.c- needs _XOPEN_SOURCE_600 or else you
get this error:
#error: "Compiler or options invalid for pre-UNIX 03 X/Open
applications and pre-2001 POSIX applications"
|
|
|
|
|
| |
For embedded builds, it'd be nice to be able to disable canberra.
Canberra is still enabled by default.
|
|
|
|
|
| |
This fixes a problem that was already separately fixed by Thomas,
in commit 575f5, but it does it more elegantly.
|
|
|
|
| |
assigned a name of their own to a default value. Fixes: 625781
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We want switching between the windows of an application to be an easily
accessible operation. The convenient and memorable keybinding is the
key above the tab key - but the keysym for that key isn't consistent
across different keyboard layouts.
Add code that figures out the key from the XKB geometry and a magic
keysym name "Above_Tab" that refers to this key and switch
the default binding for cycle_group to <Alt>Above_Tab.
https://bugzilla.gnome.org/show_bug.cgi?id=635569
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This patch fixes the drawing of <arc> theme elements to appear in the desired orientation
https://bugzilla.gnome.org/show_bug.cgi?id=631487
|
|
|
|
|
|
|
|
|
|
|
| |
Simplify the keymap loading logic by unifying the different
branches; in the reorganization this patch fixes a bug where when
we got a MappingKeyboard event we wouldn't update virtual modifiers
correctly.
Based on a patch by Thomas Thurman <tthurman@gnome.org>
https://bugzilla.gnome.org/show_bug.cgi?id=565540
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Select for XKB keyboard notification events explicitly; since GTK+
has selected for XKB events, delivery of old-school MappingNotify
events is disabled.
* Fix a bug where once a keycode was loaded for a key binding,
it would never be reassigned; we want to laod new keycodes for
all bindings that have a key symbol rather than a fixed
keycode.
[ With fixes from Owen W. Taylor <otaylor@fishsoup.net> ]
https://bugzilla.gnome.org/show_bug.cgi?id=565540
|
| |
|
| |
|
| |
|
| |
|
| |
|