summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* clutter/evdev: Move touch notification to seatJonas Ådahl2018-02-233-61/+80
|
* clutter: Silence gtk-doc warningJonas Ådahl2018-02-231-1/+2
|
* wayland: Define abstract role types as actually abstractJonas Ådahl2018-02-233-9/+9
| | | | | | | They should not be instantiated by themself, only as actual roles. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland: Add support for stable xdg-shellJonas Ådahl2018-02-2310-176/+2395
| | | | | | | | | | | This commit adds support for xdg_shell (the stable version). This was done by first copying the old xdg-shell unstable v6 implementation into a separate .c .h file pair (including various symbol renaming) then porting the old xdg-shell unstable v6 implementation to the new stable version. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland: Use helper to set shell surface windowJonas Ådahl2018-02-234-5/+25
| | | | | | | The helper deals with updating the surface output state. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland: Push actor state instead of itself pullingJonas Ådahl2018-02-2313-309/+308
| | | | | | | | | | | | | | | | | Make the Wayland objects push the state relevant to their role to the MetaSurfaceActor instead of MetaSurfaceActorWayland pulling the state from the associated surface. This makes the relationship between the actor and the objects that constructs it more clear; the actor is a drawable that the protocol objects control, not the other way around. This will make it easier to "detach" a surface actor from a surface, which is necessary when unmapping a window while the underlying surface is yet to be destroyed and potentially reused. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* surface-actor/wayland: Minor style fixesJonas Ådahl2018-02-231-5/+9
| | | | | https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* xwayland: Base Xwayland surface role object on the actor roleJonas Ådahl2018-02-231-3/+12
| | | | | | | | | The Xwayland role uses a MetaSurfaceActorWayland just so lets share logic related to it. As a side effect, wl_surface.enter/leave starts working for Xwayland surfaces. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland: Restructure surface role building blocks codeJonas Ådahl2018-02-2312-648/+834
| | | | | | | | | | | | | | | | | | | | | This commit moves out non-core wl_surface related code into separate code units, while renaming types to fit a common scheme. The changes done are: * ClutterActor based surface roles built upon MetaWalyandSurfaceRoleActorSurface. This object has been renamed to MetaWaylandActorSurface and related functionality has moved into meta-wayland-actor-surface.c. * The code related to roles backed by a MetaWindow (i.e. built upon MetaWaylandShellSurface) was moved into meta-wayland-shell-surface.c * The majority of subsurface related code was moved into into meta-wayland-subsurface.c and the object was renamed MetaWaylandSubsurface. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland/surface: Stop using deprecated g_object_newvJonas Ådahl2018-02-231-38/+38
| | | | | | | | Replace it with g_object_new_with_properties. This fixes a warning about using deprecated API. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland/xdg-shell: Minor cosmetic cleanupsJonas Ådahl2018-02-231-6/+8
| | | | | https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland/xdg-shell: Standardize xdg_positioner Wayland vfunc namingJonas Ådahl2018-02-231-32/+32
| | | | | | | | Use the convention [interface]_[request] (..) used elsewhere in the file. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland/xdg-shell: Standardize object class interface vfunc namesJonas Ådahl2018-02-231-52/+53
| | | | | | | | Follow the convention that MetaSomeObject's class vfuncs should be named meta_some_object_said_vfunc. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* wayland: Shorten MetaWaylandSurfaceRoleShellSurface nameJonas Ådahl2018-02-236-145/+140
| | | | | | | It was annoyingly long, so rename it to MetaWaylandShellSurface. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* .gitignore: Add more things to ignoreJonas Ådahl2018-02-231-0/+6
| | | | | | | Various protocol files had not been added. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
* src/Makefile.am: Remove redundant generation rulesRobert Mader2018-02-231-11/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=792203
* Update Galician translationFran Dieguez2018-02-231-5/+5
|
* Update Serbian Latin translationМилош Поповић2018-02-221-85/+132
|
* Update Serbian translationМарко Костић2018-02-221-84/+131
|
* Updated Spanish translationDaniel Mustieles2018-02-221-88/+103
|
* x11: Do not discard shape region for undecorated windowsOlivier Fourdan2018-02-221-3/+3
| | | | | | | | | | | | | | | | | mutter would discard the shape region set by the client if its matches the entire client area in meta_window_x11_update_shape_region(). However, if the window is later resized (maximized or other), the compositor will fail to update the shape region properly for undecorated windows because the shape region was discarded, which causes black areas to appear in place of the updated areas. If the client window is undecorated, keep the shape region even if when it matches the client area. https://gitlab.gnome.org/GNOME/mutter/issues/27 Closes: #27
* renderer/native: Don't use modifiers to import linear DMA bufferLouis-Francis Ratté-Boulianne2018-02-221-1/+2
| | | | | | | | | | | | | When the buffer modifier is DRM_FORMAT_MOD_LINEAR, we can use the old code path. That means not specifying any modifier parameter. It was an issue when the primary GPU was creating a linear GBM surface and that a secondary GPU (not supporting modifiers) was trying to import it. It was failing because the driver could not use the import_modifiers extension even though it could in theory easily import the buffer. https://gitlab.gnome.org/GNOME/mutter/issues/18
* native/renderer: Retrieve the right modifiers set for each GPULouis-Francis Ratté-Boulianne2018-02-221-140/+241
| | | | | | | | | | | | | | | | | We were retrieving the supported KMS modifiers for all GPUs even though what we really need to intersect between these sets of modifiers: 1) KMS supported modifiers for primary GPU if the GPU is used for scanout; 2) EGL supported modifiers for secondary GPUs (different than the primary GPU used for rendering); 3) GBM supported modifiers when creating the surface (already taken care of by gbm_surface_create_with_modifiers()); https://gitlab.gnome.org/GNOME/mutter/issues/18
* renderer/native: Use the right EGL image parameters for extra planesLouis-Francis Ratté-Boulianne2018-02-221-7/+7
| | | | | | There was a typo for modifier parameter of planes 1 & 2. https://gitlab.gnome.org/GNOME/mutter/issues/18
* configure.ac: Bump API version numberJonas Ådahl2018-02-211-1/+1
| | | | | | Better late then never. Closes: https://gitlab.gnome.org/GNOME/mutter/issues/6
* Bump version to 3.27.913.27.91-realFlorian Müllner2018-02-212-1/+49
| | | | Update NEWS.
* backends: Monitor changes in active tools' settingsCarlos Garnacho2018-02-191-3/+68
| | | | | | | | | | So the changes can be instantly applied while the tool is in proximity. Before we would just do it on proximity-in, which doesn't provide a good look&feel while modifying the tool settings in g-c-c. https://gitlab.gnome.org/GNOME/mutter/issues/38 Closes: #38
* clutter: Check the ClutterTextInputFocus has focus before filtering eventsCarlos Garnacho2018-02-181-2/+4
| | | | | | | | | | Checking correct state is responsibility of the ClutterInputFocus user, and it is indeed possible to get a focused ClutterText while its ClutterInputFocus didn't get itself focused (eg. lack of IM). https://gitlab.gnome.org/GNOME/mutter/issues/36 Closes: #36
* build: Fix distcheckCarlos Garnacho2018-02-181-0/+1
| | | | | | | | Missing protocol XML in wayland_protocols/EXTRA_DIST. https://gitlab.gnome.org/GNOME/mutter/issues/35 Closes: #35
* Update Croatian translationgogo2018-02-171-84/+131
|
* Update Brazilian Portuguese translationRafael Fontenelle2018-02-161-83/+127
|
* Update Galician translationFran Dieguez2018-02-141-94/+117
|
* wayland: Avoid clutter_input_focus method calls when unfocusedwip/carlosg/text-input-fixesCarlos Garnacho2018-02-121-0/+2
| | | | | | | | If text_input_enable() is called when there no active IM (eg. running plain mutter), some ClutterInputFocus method calls that are not allowed while unfocused will end up called, triggering critical warnings. If there is no IM return early here, all other calls are superfluous then.
* clutter/text: Be more pervasive at updating input method stateCarlos Garnacho2018-02-121-2/+9
| | | | | More concretely, ensure preedit text goes away after commit/focus_out, and update cursor position right after focus_in.
* Update Indonesian translationKukuh Syafaat2018-02-101-15/+19
|
* Change naming of GParmSpec enum id string for naming consistencyGwan-gyeong Mun2018-02-103-9/+9
| | | | | | | | | GParamSpec enum string usually follows "PROP_" prefix and PROP_LAST is used for last PROP string. https://gitlab.gnome.org/GNOME/mutter/issues/28 Closes: #28
* cogl-texture: Remove unused functionFlorian Müllner2018-02-091-279/+0
| | | | Commit d8f2f583e69f removed the only caller.
* wayland: Handle NULL event node/vendor/product on tablet methodsCarlos Garnacho2018-02-092-4/+15
| | | | | | We currently don't handle NULLs on these correctly, yet they can be so when running nested. Just refrain from sending those wp_tablet(_pad) events in that case.
* backends/x11: wacom pressure curve is a 32-bit propertyPeter Hutterer2018-02-091-2/+2
| | | | | | | | | | The property has been 32 bits since around 2011 and has not changed, mutter expects it to be 8 bits. The mismatch causes change_property to never actually change the property. https://gitlab.gnome.org/GNOME/mutter/issues/26 Closes: #26
* Update Polish translationPiotr Drąg2018-02-081-83/+111
|
* wayland: Fix handling of INCR transactionsCarlos Garnacho2018-02-071-2/+2
| | | | | | | | | | The window checks in the XPropertyEvent handler were wrong both ways, so transfers would be left stale after the first chunk was dealt with. https://gitlab.gnome.org/GNOME/mutter/issues/1 Closes: #1
* wayland: Use read_all() when reading wayland selectionsCarlos Garnacho2018-02-071-7/+6
| | | | | | | | | | | Plain input stream read() calls don't provide hard guarantees about the number of bytes read, but the async method callback sort of relies on bytes being less than requested only when reaching the end of the transmitted data. If that happens mid transfer, that doesn't bode well. This is actually the behavior of g_input_stream_read_all(), so switch to using it.
* clutter/x11: Remove video memory purge APIJonas Ådahl2018-02-072-30/+1
| | | | | | | Clutter doesn't handle it anyway, and mutter now creates the CoglRenderer object itself so we don't need this API anymore. https://bugzilla.gnome.org/show_bug.cgi?id=739178
* renderer/x11: Enable GPU memory purge error extension if availableJonas Ådahl2018-02-072-2/+1
| | | | | | | | This was done by the clutter X11 backend before prior to introducing MetaRenderer, but during that work, enabling of said extension was lost. Let's turn it on again. https://bugzilla.gnome.org/show_bug.cgi?id=739178
* cogl/x11/renderer: Silence introspection warningJonas Ådahl2018-02-071-1/+1
| | | | | | | We don't introspect CoglRenderer, so we shouldn't introspect API using it either. https://bugzilla.gnome.org/show_bug.cgi?id=739178
* Update Friulian translationFabio Tomat2018-02-061-73/+71
|
* main: Add --x11 command line argumentJonas Ådahl2018-02-061-2/+14
| | | | | | | | This is in order to force running as a X11 window manager/compositing manager. Useful for debugging and other cases where the automatic detection does not work as expected. https://gitlab.gnome.org/GNOME/mutter/merge_requests/15
* wayland: Do not fail on stalled .X11-unix entriesOlivier Fourdan2018-02-051-1/+2
| | | | | | | | | | | | | | If for whatever reason, there are stalled files in /tmp/.X11-unix/ the bind() to the abstract socket will succeed but not the bind() to the to the UNIX socket. This causes gnome-shell/mutter to fail because it cannot start Xwayland (while it could actually, by using a different display). In case of failure to bind to the UNIX socket, try the next display instead of failing, to avoid stalled entries in /tmp/.X11-unix. Closes: https://gitlab.gnome.org/GNOME/mutter/issues/13
* cogl-texture: refuse downloading textures in cogl_texture_get_data() on GLESGeorge Kiagiadakis2018-02-051-17/+5
| | | | | | | | | | | | | | | | | | | On drivers that do not support glGetTexImage2D (i.e. on GLES), cogl_texture_get_data() has a "feature" that allows it to download texture data by rendering the texture on an intermediate framebuffer object and then reading back the data from there. However, this feature requires the user to have previously set an "active" framebuffer object in the context, which makes this very tricky because it is not clear to the developer that he needs to do that in order for some code to work on GLES (of course it works on desktop GL, so nobody notices...) and additionally the code actually crashes if an active fbo is not set! This patch basically removes this feature in order to prevent the crash and is in line with how this code has evolved in cogl-2.0: https://git.gnome.org/browse/cogl/commit/?id=6d6a277b8e9a63a8268046e5258877ba94a1da5b https://bugzilla.gnome.org/show_bug.cgi?id=789961
* wayland: send shortcut inhibit “active” eventOlivier Fourdan2018-02-051-9/+3
| | | | | | | | | | | | | | The shortcut inhibitor protocol states that the “active” event should be sent every time compositor shortcuts are inhibited on behalf of the surface. However, mutter would send that event only if the surface is focused, which might not be the case if focus is on a shell surface. Send the “active” event unconditionally to match the protocol definition. Closes: https://gitlab.gnome.org/GNOME/mutter/issues/10
View Lorry Controller Status