Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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
|
|
|
|
The GDK drawing API was deprecated/removed.
https://bugzilla.gnome.org/show_bug.cgi?id=627245
|
|
|
|
With client side windows, mixing GDK event delivery with explicit calls
to XUngrabPointer() can result in GDK losing button release events
it expects to get. This means that GDK thinks there is an implicit
grab in effect when there is none and send events to the wrong window.
Avoid this by bypassing GDK's event handling for most mouse events.
We do a simplified conversion of the X event into a GdkEvent and send
it to directly to libgtk for delivery.
We make an exception when a GDK grab is already in effect - this is
needed for the correct operation of menus.
http://bugzilla.gnome.org/show_bug.cgi?id=599181
|
|
The fix depends on new API added in this cycle, so the required
GTK+ version is bumped to 2.21.1.
https://bugzilla.gnome.org/show_bug.cgi?id=572332
|
|
|
|
|
|
If the display hasn't been initialized yet, just change the
start variable and don't update the display.
https://bugzilla.gnome.org/show_bug.cgi?id=618613
|
|
https://bugzilla.gnome.org/attachment.cgi?id=133411
|
|
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=592693
|
|
|
|
When window initially maps, use the more recent of NET_WM_USER_TIME and
startup notification timestamps to compare against last known user action to
decide whether to focus the window or not. Once we show the window, clear
the initial_timestamp_set flag, so the startup notification timestamp is not
taken into account again.
Based on patch for metacity by Alexander Larsson
http://bugzilla.gnome.org/show_bug.cgi?id=573922
|
|
When started without session related command line parameters (e.g. from
gnome-session), metacity picks up client_id from the DESKTOP_AUTOSTART_ID
environment variable. Unfortunately, there is no way to distinguish if this was
passed from a config file, representing old saved session, or generated by
gnome-session, therefore load_state is attempted in each case. If the client_id
is generated, there will be no session file, and metacity will report a
warning.
Just remove the warning so that users won't always find a warning at the
start of their .xsession-errors.
https://bugzilla.gnome.org/show_bug.cgi?id=577576
|
|
|
|
This is a regression added in 333446ab.
|
|
Based on patch by Dominique Leuenberger
<dominique-gnomezilla@leuenberger.net>
https://bugzilla.gnome.org/show_bug.cgi?id=606719
|
|
There are two wrong assumptions there:
- ` being above tab is surely true for some qwerty layout, but not in
other layout like azerty (² is above the tab). We should find a clever
way to find the key above tab
- ` is proceeded in azerty keyboard (french layout) by <Alt Gr + è>. The
issue is that <Shift + è> is "7". And so, "Alt + 7" (used in some
applications like irssi, weechat, …) is <Alt + Shift + è>, which is
the reverse order to naviguate between grouped windows, and so, you
can't anymore access to this keybinding.
|
|
Was meant to be:
errno==0 && pwd!=NULL
Not:
errno==0 || pwd==NULL
https://bugzilla.gnome.org/show_bug.cgi?id=609586
|
|
The MetaDirection enumeration had META_SIDE_* values in it that
were used in some places where an enum with only four directions
was needed. Split this off into a separate enum called MetaSide
and use that enum name where appropriate.
|
|
|
|
-Replaced calls to gtk_toolbar_insert_stock with gtk_toolbar_insert
-Created appropriated GtkToolButtons
|
|
-Replaced calls to gtk_toolbar_insert_stock with gtk_toolbar_insert
-Created appropriate GtkToolButton items
|
|
Fixes part of GNOME Bug #572332
|
|
|
|
|
|
|
|
|
|
The ICE connection is opened by libSM; we can't just close it when
we get an IOError on the ICE connection; instead call SmcCloseConnection()
and mark the connection as closed. This will prevent a segfault if we
exit out of the metacity main loop and get to meta_finalize().
https://bugzilla.gnome.org/show_bug.cgi?id=604867
|
|
|
|
|
|
|
|
Looks like there are some leftovers in include/util.h:
/**
* An object which exists purely to attach signals to; this is to receive
* signals when a child process exits. The signal is "sigchld" with no detail.
*/
extern MetaNexus *sigchld_nexus;
Removing those lines fixes the build
|
|
These sounds are good candidates for caching in the sound server, to
save a bit of CPU and make reaction faster. Hence, tell libcanberra to
cache them.
|
|
GDK_WINDOW_TYPE_HINT_TOOLTIP
libcanberra generates specific tooltip popup sounds and for that
recognizes the tooltip windows by the GtkWindowTypeHint set for them.
This trivial patch simply sets the hint for the self-drawn tooltips
metacity uses.
|
|
Right now metacity issues only 1 bell event per second. This is
feels buggy when triggering multiple alarm sounds in a terminal.
This patch simple increases the limit to 1/100ms. 100ms is probably a
good choice since the HIG recommends that all user reaction should
happen within 100ms. With this applied pressing 'Left' in gnome-terminal
feels much more responsive.
https://bugzilla.redhat.com/show_bug.cgi?id=498608
|
|
The commit that removed metacity-dialog added a global SIGCHLD handler
that caused problems by (a) calling waitpid(-1) and thus breaking
g_child_watch for everyone else, and (b) doing too much from a signal
handler and sometimes causing deadlocks (bug 596200).
This removes the global handler and has each zenity user create its
own child watch to watch for exit. (It also fixes the window class of
the zenity dialogs, so that meta_window_present_delete_dialog()
will work again.)
|
|
It's not a legal function to call from a signal handler.
Instead defer until going back to the main loop.
https://bugzilla.gnome.org/show_bug.cgi?id=600864
|
|
Include the XFCE terminal program 'Terminal' in the list of terminals.
https://bugzilla.gnome.org/show_bug.cgi?id=599262
|
|
It makes more sense because the grave key is close
to the tab and escape keys which the other cycle
keybindings use.
This always works better for gnome-shell, which
switchings between applications by default with alt-tab.
The user can now alt-tab to the application they want,
and then move their finger to the grave key to select
the window they want.
|
|
|
|
|
|
|
|
* src/include/util.h:
* src/tools/metacity-window-demo.c:
* src/ui/fixedtip.c:
* src/ui/frames.c:
* src/ui/frames.h:
* src/ui/menu.c:
* src/ui/metaaccellabel.c:
* src/ui/metaaccellabel.h:
* src/ui/preview-widget.c:
* src/ui/preview-widget.h:
* src/ui/tabpopup.c:
* src/ui/theme-viewer.c:
* src/ui/themewidget.c:
* src/ui/themewidget.h:
* test/tokentest/tokentest.c:
svn path=/trunk/; revision=4193
|