Florian Müllner
333d78f338
Update .gitignore
2014-04-09 12:29:15 -07:00
Seán de Búrca
814b2dbda9
build: Create m4 directory
...
Due to changes in gnome-common git, an implicit m4 directory is no
longer created during autogen. The attached patch explicitly and
correctly specifies a macro directory.
https://bugzilla.gnome.org/show_bug.cgi?id=706787
2014-04-09 12:28:45 -07:00
Owen W. Taylor
ebbdfabed6
window-props.c: React to changes to _GTK_FRAME_EXTENTS
...
When _GTK_FRAME_EXTENTS changes, we need to redo constraints on
the window - this matters in particular if the toolkit removes
invisible borders when a window is maximized, since otherwise
the maximized window will be positioned as if it still has
invisible borders.
https://bugzilla.gnome.org/show_bug.cgi?id=714707
2014-04-09 12:20:45 -07:00
A. Walton
4396ac809b
screen: Name the guard window
...
So that extensons can recognize it, for the case where they
want to watch the window list.
https://bugzilla.gnome.org/show_bug.cgi?id=710346
2014-04-09 12:20:07 -07:00
Colin Guthrie
c2b9155979
MonitorXrandr: Mask a BadValue error on VirtualBox.
...
https://bugzilla.gnome.org/show_bug.cgi?id=707563
2014-04-09 12:19:11 -07:00
Robert Ancell
f68d65a5ae
xrandr: Use specified output property name for backlight control
...
Backlight controls are set using the "BACKLIGHT" XRANDR output property.
This should be "Backlight" according to the XRANDR spec [1].
Some drivers (Intel) export both properties and some only the specified property (nvidia).
Users of drivers that only export the specified property cannot change their backlight using XRANDR.
[1] http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt section 9.1
https://bugzilla.gnome.org/show_bug.cgi?id=723606
2014-04-09 12:17:58 -07:00
Giovanni Campagna
42f267bb50
MonitorManager: make sure to pass the right sizes to vararg functions
...
A gulong is not enough to get 64 bits in all arches, so we must
cast it, or we can corrupt the stack.
This was downstream bug bugzilla.redhat.com/show_bug.cgi?id=1002055
https://bugzilla.gnome.org/show_bug.cgi?id=707267
2014-04-09 12:14:26 -07:00
Giovanni Campagna
e215f3f5eb
monitor-config: prevent assert that at least one output is connected
...
Apparently some connector technologies don't distinguish between
on and off, and there might be valid use cases for running without
any connected monitor.
In that case, just avoid any configuration at all.
https://bugzilla.gnome.org/show_bug.cgi?id=709009
2014-04-09 12:13:32 -07:00
Florian Müllner
7ac66faa72
tower: Fix erroneous return value
...
The function's return value is void, not gboolean.
2014-04-09 12:10:24 -07:00
Robert Bragg
d0b870d3a9
tower: make sure not to blend when updating tower
...
Each level in the tower is initialized by binding the texture for that
level to an offscreen framebuffer and rendering the previous level as a
textured rectangle. The problem was that we were blending the previous
level with undefined data so argb32 windows with transparencies would
result in artefacts. This makes sure to disable blending when drawing
the textured rectangle.
2014-04-09 12:10:17 -07:00
Jasper St. Pierre
99ad5c00a7
texture-tower: Remove CPU codepath for mipmap generation
...
The CPU codepath for mipmapping is unusably slow, and we expect modern
graphics cards with modern TFP/FBO support.
2014-04-09 12:10:00 -07:00
Jasper St. Pierre
797c46ba7d
events: Fix event handling for window menus under X11
...
We need to pass XI_Enter / XI_Leave events for GTK+ windows to GTK+,
rather than eating them.
2014-04-09 11:38:49 -07:00
Nirbheek Chauhan
ab0bd59f5e
window-props: _NET_WM_WINDOW_OPACITY range is 0xffffffff to 0
...
After reading the atom, scale the value from 0xffffffff to 0xff. Not doing so
causes Clutter to truncate the opacity value, and only read the last two digits.
Hence, 0x7fffffff (50%) becomes 0xff (100%).
https://bugzilla.gnome.org/show_bug.cgi?id=727874
2014-04-09 16:40:10 +02:00
Rui Matos
feca0fb512
xwayland: Re-sync input focus when associating a surface to a window
...
When the MetaWindow is created we don't have the surface yet and thus
we can't set input focus to it so we need to try again when we get the
surface.
2014-04-09 11:20:28 +02:00
Jasper St. Pierre
2f229c3928
display: Remove code to calculate the above-tab keycode
...
We always know it will be KEY_GRAVE + 8.
2014-04-07 17:56:00 -04:00
Jasper St. Pierre
a730361d6c
Use libxkbcommon keysym names everywhere
2014-04-07 17:56:00 -04:00
Jasper St. Pierre
db058d4a81
keybindings: Use xkb_keysym_get_name
2014-04-07 17:56:00 -04:00
Jasper St. Pierre
15cf804dbc
keybindings: Eliminate the use of the stored modmap
...
We can simply check the XKB keysym here to see if it's a modifier.
2014-04-07 17:55:59 -04:00
Jasper St. Pierre
b38b037092
keybindings: Don't bother saving num_lock / caps_lock in MetaDisplay
...
It's unused outside of this one function.
2014-04-07 17:55:58 -04:00
Jasper St. Pierre
42bcad6549
display: Ignore the modmask passed into meta_display_begin_grab_op
...
A careful analysis of mutter's codebase shows that nothing actually
passes anything but 0 to this. gnome-shell has one instance, but it's
most likely a mistake.
Remove the grab_mask field and the one place in keybindings.c that uses it.
The parameter to begin_grab_op is left in for API compatibility reasons.
2014-04-07 17:45:52 -04:00
Jasper St. Pierre
b0ea0afd2f
display: Remove meta_display_get_ignored_modifier_mask
...
It's unused, in both here and in gnome-shell.
2014-04-07 17:16:29 -04:00
Jasper St. Pierre
1d08d75108
keybindings: Rename and move keysym_to_keycode
...
This makes it more what it's actually doing.
2014-04-07 16:02:08 -04:00
Jasper St. Pierre
4daf20483d
keybindings: Handle META_KEY_ABOVE_TAB in get_keycodes_for_keysym
...
We're going to switch to get_keycodes_for_keysym for the other
bindings, so add that special case here.
2014-04-07 16:01:24 -04:00
Jasper St. Pierre
96b6dcec01
display: Kill some bad whitespace
2014-04-07 16:00:17 -04:00
Jasper St. Pierre
9fe5a3b407
keybindings: Fix style
2014-04-07 16:00:17 -04:00
Jasper St. Pierre
a7d4713393
accel-parse: Add a notice about where the code came from
2014-04-07 11:25:16 -04:00
Jasper St. Pierre
4d4ecae2a1
accel-parse: Clean up trailing whitespace
2014-04-07 11:24:23 -04:00
Jasper St. Pierre
545c3b6678
accel-parse: Clean up error handling
...
Now that we have the code in-tree, we can change the API to actually
report an error rather than checking afterwards.
2014-04-07 11:21:36 -04:00
Jasper St. Pierre
e70f336a09
accel-parse: Use libxkbcommon for keysym parsing
...
This kills our dependency on GTK+ / GDK entirely.
2014-04-07 11:19:41 -04:00
Jasper St. Pierre
806f1742ac
accel-parse: Switch code to output MetaVirtualModifier directly
2014-04-07 11:19:40 -04:00
Jasper St. Pierre
0dc63f395d
accel-parse: Remove support for <Release>
2014-04-07 11:15:01 -04:00
Jasper St. Pierre
616f1a09b1
accel-parse: Add keycode parsing as well
2014-04-07 11:15:01 -04:00
Jasper St. Pierre
50e69109b6
accel-parse: Integrate Above_Tab parsing code directly into our copy
2014-04-07 11:15:01 -04:00
Jasper St. Pierre
242784d3e4
accel-parse: Copy the code from GTK+ in-tree
...
We can't use GTK+ for accelerator parsing under Wayland, since we
don't want to go through Xwayland to make that happen.
2014-04-07 11:14:35 -04:00
Jasper St. Pierre
0466fe9301
Move meta_ui_parse_accelerator into core/
...
We're currently using GTK+ for this, but we'll stop doing that fairly
quickly and instead just copy the GTK+ code in-tree.
2014-04-07 10:59:46 -04:00
Jasper St. Pierre
dbf5d8f9bc
ui: Kill off meta_ui_accelerator_name
...
It's unused.
2014-04-07 10:46:50 -04:00
Jasper St. Pierre
b9e9595e8b
errors: Kill off meta_error_trap_push_with_return
...
It isn't special; it's just an alias for meta_error_trap_push.
2014-04-07 10:37:03 -04:00
Jasper St. Pierre
75de29f5f7
errors: Remove vestigals of old error trap implementation
2014-04-07 10:37:03 -04:00
Jasper St. Pierre
e2b24092d6
events: Don't pass any X input events on to Clutter / GTK+
2014-04-07 10:37:02 -04:00
Jasper St. Pierre
0e6570b09b
events: Early exit when we get a SN notification event
...
Nothing else needs to see this.
2014-04-07 10:37:02 -04:00
Jasper St. Pierre
840378ae68
xprop: Don't use GDK for reading text properties
2014-04-07 10:37:02 -04:00
Jasper St. Pierre
4752776ebf
ui: Don't add our filter function twice
2014-04-06 15:19:04 -04:00
Jasper St. Pierre
c40868b239
xwayland: Fix rendering
...
Since we get the ClientMessage after the surface is created, there's
no good way to synchronize the two streams. In this case, what we
need to do is delay the surface commit until after we get the
ClientMessage. Ideally, we'd be using a better surface system overall
where committing the surface didn't depend on what type it is, but
oh well, this is a good short-term hack for now.
2014-04-02 13:24:58 -04:00
Jasper St. Pierre
a21e7a2188
wayland: Move surface_set_buffer back into the commits
...
For XWayland support, we need to delay the buffer set until after
we do the typechecking, as we need to bail out early in that case.
2014-04-02 13:24:58 -04:00
Jasper St. Pierre
371fba6843
wayland: Move the commit implementation to the top
...
We're going to need to expose commit as a public method for XWayland
support, so decouple it from the handler implementation.
2014-04-02 13:24:57 -04:00
Jasper St. Pierre
be02fa1120
xwayland: Switch to the new Xwayland DDX
2014-04-02 13:24:57 -04:00
Jasper St. Pierre
43730f1660
xwayland: Switch to SIGUSR1 to know when the X server has finished init
...
This is effectively the same, but since we lose the xserver.xml protocol
in the new XWayland DDX, we have to use SIGUSR1 anyway, so might as well
switch over now.
2014-04-02 13:16:10 -04:00
Jasper St. Pierre
4f609dbf5e
xwayland: Don't use glib after forking
...
glib doesn't have any guarantee about working after forking.
We can get away with it, but we're better off just not using it.
2014-04-02 13:04:31 -04:00
Jasper St. Pierre
2a7d12ba14
xwayland: Make failing to exec a fatal error
2014-04-02 13:03:29 -04:00
Jasper St. Pierre
c4c0b5f0ab
xwayland: Detect a fail to fork
2014-04-02 13:03:17 -04:00