647743aa5f
Revert "window-wayland: Don't enter the only-moving path for Wayland
...
resizes"
We're going to use the old code structure now.
This reverts commit 23ae11043f
2014-04-28 16:23:38 -04:00
e94f169d4e
Revert "window-wayland: Make sure to save where the position for server-initiated resizes"
...
This is wrong for client-initiated resizes now.
This reverts commit e6b0525c70
2014-04-28 16:23:38 -04:00
e6b0525c70
window-wayland: Make sure to save where the position for server-initiated resizes
...
For the server-initiated resize case, like unmaximize or some forms
of tiling, we dropped the x/y of the server-assigned rectangle on the
floor, which meant the surface didn't move to where it needed to be in
that case. Now, save it internally, and combine it with the dx/dy passed
in during attaches to figure out where we actually need to be.
This fixes incorrect surface placement after unmaximization.
2014-04-28 16:11:10 -04:00
23ae11043f
window-wayland: Don't enter the only-moving path for Wayland resizes
...
We'll be adding additional code here for "correct" moving soon, so
we need to make sure not to do it for Wayland resizes.
2014-04-28 16:11:09 -04:00
78657dafca
window-wayland: Clean up a bit
2014-04-28 16:11:09 -04:00
0f47eae33a
window-wayland: Split an if statement in two
2014-04-28 16:11:09 -04:00
2209eac2bf
constraints: Make meta_window_constrain take window geometry rects
...
Remove extend_by_frame and unextend_by_frame. Use a dumb hack in
window.c to translate into window geometry in back. We'll soon track
all rectangles in MetaWindow in terms of the window geometry.
2014-04-28 16:11:09 -04:00
aed6d4fbb7
default: Remove the maximize effect
...
It looks awful, and doesn't work with Wayland at all for some
reason, which means that maximize seems to "hang" for half a
second. Just trash it.
2014-04-28 15:20:49 -04:00
270c7abd3c
default: Remove the unmaximize implementation
...
It does nothing.
2014-04-28 15:20:48 -04:00
e2bd15541b
default: Remove unused internal state tracking
2014-04-28 15:20:48 -04:00
9607513e62
backend-x11: Fix cursor position under nested
2014-04-28 13:29:45 -04:00
18730f2a5e
backend-x11: Take grabs on the stage window
...
This means that grabs will be reported with respect to the
stage window, and that our event coordinates will be more
correct under nested.
2014-04-28 13:29:31 -04:00
4e584c2cf0
display: Don't call x11 backend code when running native
...
https://bugzilla.gnome.org/show_bug.cgi?id=729044
2014-04-27 20:24:15 +02:00
d1619e4f53
wayland-pointer: Remove the conditional around the surface actor too
...
The actor should always exist.
2014-04-27 10:39:19 -04:00
c8d0a66921
wayland-surface: Ignore bufferless damage
...
Instead of letting a buggy client kill us.
2014-04-27 16:18:09 +02:00
dd4d6af185
wayland-surface: Only call process_damage when we have any damage
...
This fixes a crash when a client commits a surface
without attaching a buffer.
2014-04-27 16:12:02 +02:00
1016e2555a
Updated Hebrew translation
2014-04-27 03:52:38 +03:00
657318d4d3
meta-wayland-pointer: Remove the surface->window conditional
2014-04-25 20:38:24 +02:00
f051e05b0a
meta-wayland-pointer: Transform coordinates relative to the surface_actor
...
Not the window_actor ..
2014-04-25 20:36:46 +02:00
ca75513880
prefs: Add center-new-windows setting
2014-04-25 15:26:24 +02:00
63f1a10e33
compositor: Don't select for weird events on the COW/stage
...
Talking it over with Owen, we weren't sure why this was here.
At one point, we were creating a foreign stage window, so potentially
Clutter didn't select for its own events, but now we're using a standard
stage window, so this seems weird.
Why we did it on the COW, nobody knows. Maybe copy/paste bugginess?
2014-04-24 16:26:21 -04:00
14f839c53c
window: Only grab/ungrab buttons/keys on X11 windows
2014-04-24 16:26:21 -04:00
ebb6847bd1
ui: Don't use grab ops for grab negotation
...
Grab operations are now always taken on the backend connection, and
this breaks GTK+'s event handling.
Instead of taking a grab op, just do the handling ourselves. The
GTK+ connection will get an implicit grab, which means pointer /
keyboard events won't be sent to the rest of mutter, which is good.
2014-04-24 13:36:40 -04:00
c5d4f4a245
backend-x11: Split out event translation to another method
...
Keep the indentation from getting too hairy.
2014-04-24 12:12:54 -04:00
a027937ccc
backend-x11: Set the proper coordinates on the spoofed device event
...
When we click on a window with a passive grab, then the event_x
and event_y will be relative to that window, instead of relative to
the stage, which means that picking will be wrong.
Forcibly using root_x / root_y breaks nested mode. Nested mode is
a testing mode that should be replaced by a DRI3-enabled Xephyr,
though. It's getting too hairy to support properly.
2014-04-24 12:12:54 -04:00
925075ddaf
compositor: Don't select for stage events on the UI X11 connection
2014-04-24 12:12:53 -04:00
41de208f31
compositor: Also ungrab the VCP when beginning a modal
...
XXX: This should not be needed. We need to figure out why
there's a grab on the UI connection.
2014-04-24 11:26:12 -04:00
c8e3b52160
keybindings: Simplify
2014-04-24 11:26:11 -04:00
2c53919462
keybindings: Remove two extra error traps
2014-04-24 11:26:11 -04:00
a6f3534ff0
display: Set the cursor theme on the backend display as well
2014-04-24 11:26:11 -04:00
490f1a6249
display: Simplify cursor theme handling
2014-04-24 11:26:10 -04:00
5b83bfb1db
display: Make sure to ungrab the pointer before starting a grab op
...
Now that we grab devices on the X11 connection, we can run into
cross-connection issues. Since GTK+ frames are on the UI connection,
they'll get the passive grab when we click on them. Forcibly ungrab
on GTK+'s connection before attempting to take a grab on the backend
connection ourselves.
2014-04-24 11:26:10 -04:00
1ef06207a4
keybindings: Add two extra checks for key grab binding
2014-04-24 11:26:10 -04:00
0a6fa202a8
Updated Indonesian translation
2014-04-24 06:18:44 +00:00
18d609ad6d
window: Don't use clutter_stage_get_default
...
It doesn't work, for the same reasons.
2014-04-23 17:01:51 -04:00
c95c501a5b
meta-wayland-surface: Clip damage to buffer dimensions
...
A client can send us damage that exceeds the buffer size, protect against that
by clipping the damage to the buffer's region.
2014-04-23 22:32:17 +02:00
8c5da24401
keybindings: Fix keybindings
...
Attach them to the backend's X11 connection.
This breaks the overlay key state machine for native right now.
We'll fix it back up soon.
2014-04-23 16:29:34 -04:00
01a773ed5a
backend-x11: Don't use clutter_stage_get_default
...
It turns out Clutter doesn't actually set the stage as the default
when creating a new one, so this creates a new stage that then dies.
2014-04-23 16:01:02 -04:00
2435d132ac
Revert "Update to latest xdg-shell protocol"
...
This reverts commit eed03d38b0
2014-04-23 16:01:02 -04:00
72c65cbff0
display: Take passive grabs on the backend connection
2014-04-23 15:43:34 -04:00
97074ccdad
backend-x11: Fix leak of the event data
2014-04-23 15:43:34 -04:00
6111bb9dec
backend-x11: Adapt a consistent naming scheme for the event struct
2014-04-23 15:43:34 -04:00
eed03d38b0
Update to latest xdg-shell protocol
2014-04-23 14:23:13 -04:00
e9eb3c32a9
compositor: Move event spoofing code to MetaBackendX11
...
This is now where we handle device events.
2014-04-23 14:23:13 -04:00
61b714c666
compositor: Remove "exclusive is exclusive" codepath
...
We now handle input events in the backend.
2014-04-23 14:23:13 -04:00
e9263d25b9
compositor: Take modal grabs through the backend as well
2014-04-23 14:23:12 -04:00
d590626017
compositor: Select for input on the output window the right display
2014-04-23 14:23:12 -04:00
fdd43fc2d9
backend-x11: Add KeyPress / KeyRelease to mask
2014-04-23 14:23:12 -04:00
4cbf420b4b
idle-monitor-xsync: Clean up includes
...
Conflicts:
src/backends/x11/meta-idle-monitor-xsync.c
2014-04-23 13:27:11 -04:00
fd373948d2
idle-monitor-xsync: Retrieve your xdisplay from the backend
2014-04-23 13:27:11 -04:00
