sungmg/mutter-performance-source
1
0
Fork 0
Code Activity
5831 commits 14 branches 4 tags 92 MiB
Commit graph

5831 commits

This branch
This branch
All branches
Author SHA1 Message Date
Florian Müllner
a6c51addac prefs: Annotate meta_prefs_get_button_layout() 
https://bugzilla.gnome.org/show_bug.cgi?id=689263
 2013-01-10 00:10:50 +01:00
Florian Müllner
54a3847a5e common: Annotate MetaButtonLayout 
https://bugzilla.gnome.org/show_bug.cgi?id=689263
 2013-01-10 00:10:50 +01:00
Florian Müllner
5a8473e226 prefs: Do not leave junk values in unused button_layout fields 
MetaButtonLayout is extremely unfriendly for introspection: its fields
are arrays of a fixed length, but the actual length is determined by
a custom stop value (e.g. not NULL / 0).
Without API changes this will never work nicely in introspection, but
we can at least make it work; start by filling up unused fields with
the stop value rather than leaving it at random values.

https://bugzilla.gnome.org/show_bug.cgi?id=689263
 2013-01-10 00:10:50 +01:00
Jasper St. Pierre
5c33b0d768 theme-viewer: use the same GtkStyleContext as mutter usually renders 
https://bugzilla.gnome.org/show_bug.cgi?id=690317
 2013-01-09 14:06:24 -05:00
Jasper St. Pierre
22a3126a2b theme: Make meta_frame_draw_theme take a GtkStyleContext instead of a widget 
The style context of the widget is rarely what we want. We won't
fix this to be a MetaFrames style context yet; this just changes
the internal API.

https://bugzilla.gnome.org/show_bug.cgi?id=690317
 2013-01-09 14:06:24 -05:00
Jasper St. Pierre
9596c24f83 plugin-manager: Remove a bogus check 
We dereference the plugin_mgr in the initializer above,
so it's wrong.

https://bugzilla.gnome.org/show_bug.cgi?id=690609
 2013-01-09 14:06:24 -05:00
Alexander Shopov
86d6baf30f Updated Bulgarian translation 2013-01-09 06:15:06 +02:00
Jasper St. Pierre
3a3be74e37 Remove some server calls for core devices 
These were missed in the first porting.

https://bugzilla.gnome.org/show_bug.cgi?id=691363
 2013-01-08 15:54:50 -05:00
Jasper St. Pierre
f57d64337b display: Use XI2 constants for mode/detail focus event values 
This makes no function difference, except conceptual clarity.

https://bugzilla.gnome.org/show_bug.cgi?id=691363
 2013-01-08 15:54:50 -05:00
Jasper St. Pierre
e69fcc860c display: Remove some more core events 
I apparently forgot to remove these.

https://bugzilla.gnome.org/show_bug.cgi?id=691363
 2013-01-08 15:54:50 -05:00
Jasper St. Pierre
afbca61524 main: Remove call to clutter_x11_enable_xinput 
The call is deprecated and is called by default upstream.

https://bugzilla.gnome.org/show_bug.cgi?id=691363
 2013-01-08 15:54:50 -05:00
Jasper St. Pierre
66d37e06ba compositor: Remove unused code fetching _XSETROOT_ID 
We don't use this atom anywhere, so don't bother fetching it.

https://bugzilla.gnome.org/show_bug.cgi?id=691363
 2013-01-08 15:54:50 -05:00
Colin Walters
7e2d6cb6ec README: Minor update, really just to trigger a rebuild 
...after cogl bumped soname.
 2013-01-05 14:16:57 -05:00
Debarshi Ray
b9f775fe02 ui: Suppress warnings from -Werror=maybe-uninitialized 2013-01-03 17:30:44 +01:00
Jasper St. Pierre
90cf43da9f display: Expose the xinput opcode 
This is needed by the shell to filter out certain events

https://bugzilla.gnome.org/show_bug.cgi?id=690590
 2013-01-02 13:41:56 -05:00
Matthias Clasen
bab51cbbe4 Remove unnecessary python check 
A grep for fix-meta-rectangle.py in the source tree comes up
empty, and building mutter works just fine without AM_PATH_PYTHON.

https://bugzilla.gnome.org/show_bug.cgi?id=690956
 2013-01-02 08:01:14 -05:00
Nilamdyuti Goswami
e782426736 Assamese translation updated 2012-12-27 21:33:18 +05:30
Rafael Ferreira
1071e9970f Updated Brazilian Portuguese Translation 2012-12-27 03:56:51 -02:00
Piotr Drąg
5d64bdf3d9 Updated Polish translation 2012-12-26 21:41:21 +01:00
Yaron Shahrabani
8012a315e3 Updated Hebrew translation. 2012-12-26 19:50:51 +02:00
Daniel Mustieles
acd6df34da Updated Spanish translation 2012-12-26 11:59:29 +01:00
Giovanni Campagna
6431abbc85 Check that the application is responding when activating a window 
Currently, we ping windows only when attempting to delete them, but
if the application is not responding, we want to show the dialog
as soon as possible. Given that we cannot be passively notified that
the window stopped responding with the current X11 protocol, a good
workaround is to ping the window when activating it.
If the window stops responding while active, it is expected the user
will try to switch window or open the overview, and when coming back
he'll get the failure dialog.

https://bugzilla.gnome.org/show_bug.cgi?id=684340
 2012-12-25 18:39:10 +01:00
Giovanni Campagna
57ff0f7071 MetaWindow: add a public method for checking if the application is responding 
Add meta_window_check_alive(), which is a simple wrapper over
meta_display_ping_window(), and takes care of showing the "Application
is not responding dialog" if needed.

https://bugzilla.gnome.org/show_bug.cgi?id=684340
 2012-12-25 18:39:09 +01:00
Adel Gadllah
2a2ac52726 automaximize: Make it optional 
Make automaximize optional by adding a gsetting "auto-maximize"
(defaults to true).

https://bugzilla.gnome.org/show_bug.cgi?id=680990
 2012-12-25 13:37:22 +01:00
A S Alam
a91eeb24d4 update Punjabi Translation for master 2012-12-25 08:50:47 +05:30
Fran Diéguez
581960abc8 Updated Galician translations 2012-12-24 23:03:34 +01:00
Khaled Hosny
3a307b5d24 Update Arabic translation 2012-12-24 13:19:00 +02:00
Jasper St. Pierre
4e21d5d610 ui: Don't use deprecated GtkStyleContext API 
Update for deprecations.

https://bugzilla.gnome.org/show_bug.cgi?id=690593
 2012-12-23 03:17:26 -05:00
Daniel Mustieles
02c2cf1960 Updated Spanish translation 2012-12-21 12:26:57 +01:00
Ray Strode
748064678f prefs: drop errnoneous semi-colon 
This fixes a compiler warning and spurious
enqueuing of WORKSPACE_NAMES change.

https://bugzilla.gnome.org/show_bug.cgi?id=690573
 2012-12-20 14:27:26 -05:00
Yaron Shahrabani
982d554450 Updated Hebrew translation. 2012-12-20 13:29:07 +02:00
Mattias Põldaru
0e5f8997cf [l10n] Updated Estonian translation 2012-12-19 18:23:18 +02:00
Giovanni Campagna
6111d3ee4a window: recompute modal dialog attached status when the window type changes 
We want to maintain the invariant that an attached modal dialog is always
of type MODAL_DIALOG, so recompute is_attached_dialog() when the window
type changes.

https://bugzilla.gnome.org/show_bug.cgi?id=690454
 2012-12-18 23:18:58 +01:00
Adel Gadllah
3876a1a192 Support bypass compositor hints 
Add support for _NET_WM_BYPASS_COMPOSITOR and _NET_WM_DONT_BYPASS_COMPOSITOR
as proposed here: https://mail.gnome.org/archives/wm-spec-list/2012-February/msg00010.html

https://bugzilla.gnome.org/show_bug.cgi?id=683020
 2012-12-18 19:02:34 +01:00
Florian Müllner
6f3ae06362 Bump version to 3.7.3 
Update NEWS
 2012-12-18 13:31:41 +01:00
Rui Matos
7d7b859b40 Fix 'comparison between signed and unsigned integer' compiler errors 2012-12-17 12:30:01 +00:00
Florian Müllner
d78de379cc keybindings: Give dynamic keybindings a keybindings action 
https://bugzilla.gnome.org/show_bug.cgi?id=682315
 2012-12-17 12:00:55 +00:00
Piotr Drąg
576384a73b Updated Polish translation 2012-12-16 02:50:03 +01:00
Jasper St. Pierre
2fcbc467e8 keybindings: Fix whitespace and alignment 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 18:15:23 -05:00
Jasper St. Pierre
6139bc77ec Remove support for Core Events 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 18:15:23 -05:00
Jasper St. Pierre
c1ac9d1dff ui: Use XI2 to fake GDK events 
This removes our final dependency on Core Events, meaning
we can remove support code for them soon.

This commit is a bit ugly as it requires ui having a dependency on
core, but this is already a hack, so this is thus a hack inside a
hack, and two hacks make a right or however that goes.

https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 18:15:23 -05:00
Jasper St. Pierre
945c530354 display: Add spew for XI2 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 18:15:22 -05:00
Jasper St. Pierre
774ceec243 Select for XI2 events everywhere else 
In random places that are not grabs, we selected for events on
things like the root window, stage window, COW and more. Switch
these over to using the proper XI2 APIs.

https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 17:14:06 -05:00
Jasper St. Pierre
7c20621112 keybindings: Grab keys with XI2 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 17:14:06 -05:00
Jasper St. Pierre
afcdfd158f keybindings: Grab keyboard with XI2 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 17:14:06 -05:00
Jasper St. Pierre
8fb9e0072c display: Grab buttons with XI2 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 17:14:06 -05:00
Jasper St. Pierre
c1b8e0ac8f display: Use XInput2 to grab the pointer 
As calling XIGrabDevice multiple times will change it, just
drop the XChangeActivePointerGrab path and just go down the
XIGrabPointer path always.

https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 17:14:06 -05:00
Jasper St. Pierre
c90765370d window: Pass the grab timestamp when updating the resize grab 
Since XChangeActivePointerGrab doesn't have a direct equivalent
in XI2, we need to make sure we don't re-grab with a newer
tiemstamp.
 2012-12-13 17:06:00 -05:00
Jasper St. Pierre
8931b8026e compositor: Identify XI2 events as grabbed events 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 16:36:43 -05:00
Jasper St. Pierre
55251aa986 compositor: Use XInput2 to grab the pointer/keyboard 
https://bugzilla.gnome.org/show_bug.cgi?id=688779
 2012-12-13 16:36:42 -05:00