summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* constraints: CSD windows need to have their titlebar kept onscreen tooJasper St. Pierre2014-01-211-1/+0
| | | | | | | GTK+ CSD windows are considered undecorated by the code, so we should not force ourselves to only run on decorated windows. https://bugzilla.gnome.org/show_bug.cgi?id=719772
* Updated Galician translationsFran Diéguez2014-01-201-232/+239
|
* Updated Brazilian Portuguese translationEnrico Nicoletto2014-01-191-235/+242
|
* Revert "Updated Brazilian Portuguese translation"Rafael Ferreira2014-01-191-242/+235
| | | | This reverts commit eb1085bfe684a9593a416dcc260a32f636ef02c2.
* Updated Brazilian Portuguese translationRafael Ferreira2014-01-191-235/+242
|
* shaped-texture: Make CullableJasper St. Pierre2014-01-163-124/+69
| | | | | | Make MetaWindowActor chain up to the generic default MetaCullable implementation, and remove the helper methods for MetaSurfaceActor and MetaShapedTexture.
* cullable: Use relative actor coordinates for cullingJasper St. Pierre2014-01-163-13/+10
| | | | This ensures that nested cullables work fine.
* Bump version to 3.11.43.11.4Florian Müllner2014-01-152-1/+17
| | | | Update NEWS.
* Properly set the number of components on the CoglTextureRectangleJasper St. Pierre2014-01-134-48/+16
| | | | | | | We need to set the number of components on the CoglTextureRectangle to prevent wasting too much GPU memory. As we need to do this before we call cogl_texture_set_region, just remove the meta_texture_rectangle_new wrapper, and make callers call cogl_texture_rectangle_new_with_size directly.
* Update for Cogl API breaksJasper St. Pierre2014-01-136-20/+5
|
* window: Atomically unmaximize both directions from a _NET_WM_STATE ClientMessageJasper St. Pierre2014-01-131-23/+13
| | | | | | | | | | | | | | | | When GDK sends an unmaximize _NET_WM_STATE ClientMessage, it tells us to remove the _NET_WM_STATE_MAXIMIZED_HORZ and _NET_WM_STATE_MAXIMIZED_VERT states. Before this time, it would independently call: meta_window_unmaximize (window, META_MAXIMIZE_HORIZONTAL); meta_window_unmaximize (window, META_MAXIMIZE_VERTICAL); Which, besides being foolishly inefficient, would also mess up our saved_rect tracking, causing the window to only look like it was unmaximized vertically. Make this code more intelligent, so it causes us to unmaximize in one call. https://bugzilla.gnome.org/show_bug.cgi?id=722108
* Updated Greek translationDimitris Spingos2014-01-131-232/+239
|
* Updated Hebrew translationYosef Or Boczko2014-01-131-232/+239
|
* Updated obsolete FSF postal address in COPYINGAndika Triwidada2014-01-121-21/+20
| | | | Fixed https://bugzilla.gnome.org/show_bug.cgi?id=721517 #1
* Changed obsolete FSF postal address into generic URL.Andika Triwidada2014-01-12137-413/+138
| | | | Fix https://bugzilla.gnome.org/show_bug.cgi?id=721517 #2
* [l10n] Updated Italian translation.Milo Casagrande2014-01-101-107/+113
|
* monitor: Suppress -Werror=unused-variableDebarshi Ray2014-01-091-1/+0
| | | | | | Fallout from 477acddf642d735ef036a95fda6f4d7f6b522fd1 https://bugzilla.gnome.org/show_bug.cgi?id=721674
* Updated Spanish translationDaniel Mustieles2014-01-081-108/+116
|
* window: don't grab server during calc_showingDaniel Drake2014-01-071-7/+0
| | | | | | | | | | | | | | | This grab was added in commit caf43a123f40d3a68599ac5453a79759b828e8f0 https://bugzilla.gnome.org/show_bug.cgi?id=381127 to minimize window flickering when switching workspaces. While this grab is held, some signals are emitted to the shell, which can lead to deadlocks (reproduced under Mali binary OpenGLESv2 drivers). Now that we are a compositing window manager, we do not have to worry about flickers, this grab should no longer be necessary. https://bugzilla.gnome.org/show_bug.cgi?id=721709
* monitor: improve heuristic to determine display output nameCosimo Cecchi2014-01-071-25/+40
| | | | | | | | | | | | | | | | | | | | | Under some circumstances, for example when the display controller driver doesn't report back the correct EDID, or under VirtualBox, Mutter returns suboptimal strings for an output display name, leading to funny labels like 'Unknown 0"', or '(null) 0"' in the Settings panel. This commit improves our heuristic in three ways: - we now avoid putting inches in the display name if either dimension is zero - we use the vendor name in case we're not able to lookup its PnP id from the database. Previously we would have passed over '(null)' - as a special edge-case, when neither inches nor vendor are known, we use the string 'Unknown Display' Finally, we make the combined vendor + inches string translatable, as different languages might want to move the size part of the string to a position different than the end. https://bugzilla.gnome.org/show_bug.cgi?id=721674
* Updated Greek translationDimitris Spingos2014-01-071-357/+311
|
* Reduce server grabs during window creationDaniel Drake2014-01-063-12/+5
| | | | | | | | | | | | | | | | | | | | | | Remove some obvious server grabs from the window creation codepath, also ones that are taken at startup. During startup, there is no need to grab: we install the event handlers before querying for the already-existing windows, so there is no danger that we will 'lose' some window. We might try to create a window twice (if it comes back in the original query and then we get an event for it) but the code is already protected against such conditions. When windows are created later, we also do not need grabs, we just need appropriate error checking as the window may be destroyed at any time (or it may have already been destroyed). The stack tracker is unaffected here - as it listens to CreateNotify and DestroyNotify events and responds directly, the internal stack representation will always be consistent even if the window goes away while we are processing MapRequest or similar. https://bugzilla.gnome.org/show_bug.cgi?id=721345
* meta_window_new: clean up error handlingDaniel Drake2014-01-061-42/+20
| | | | | | | | | | | | | | The return code of XGetWindowAttributes() indicates whether an error was encountered or not. There is no need to specifically check the error trap. The trap around XAddToSaveSet() was superfluous. We have a global error trap to ignore any errors here, and there is no need to XSync() as GDK will later ignore the error asynchronously if one is raised. Also move common error exit path to an error label. https://bugzilla.gnome.org/show_bug.cgi?id=721345
* screen: use stack tracker for initial window queryDaniel Drake2014-01-061-8/+6
| | | | | | | | | | | | In meta_screen_manage_all_windows() we can use our own stack tracker to get the list of windows - no need to query X again. A copy is needed because the stack gets modified as part of the loop. Specifically, meta_stack_tracker_get_stack() at this time returns the predicted stack, and meta_window_new() performs a few operations (e.g. framing) which cause immediate changes to the predicted stack. https://bugzilla.gnome.org/show_bug.cgi?id=721345
* frame: remove unnecessary server grabDaniel Drake2014-01-061-13/+0
| | | | | | | | | | | | | | | | meta_window_ensure_frame() creates its own grab and has a comment claiming that it must be called under a grab too. But the reasoning given in the comment does not seem relevant here. We only frame non-override-redirect windows, so we are creating the frame in response to MapRequest. There is no way that the child could receive a MapNotify at this point, since that only happens much later, once we go through the CALC_SHOWING queue and call XMapWindow() from meta_window_show(). Remove the unnecessary grab. https://bugzilla.gnome.org/show_bug.cgi?id=721345
* Discourage server grabsDaniel Drake2014-01-061-1/+12
| | | | | | | | | | | | Server grabs are not as evil as you might expect, but there is agreement in that their usage should be limited. Server grabs can cause things to go rather wrong when mutter emits a signal while it has grabbed the server. If the receiver of that signal waits for a synchronous action performed by another client, then you have a deadlock. This happens with Mali binary GLESv2 drivers :( https://bugzilla.gnome.org/show_bug.cgi?id=721345
* Remove meta_window_new_with_attrsDaniel Drake2014-01-064-157/+85
| | | | | | | | | | | | The compositor code used to handle X windows that didn't have a corresponding MetaWindow (see commit d538690b), which is why the attribute query is separated. As that doesn't happen any more, we can clean up. No functional changes. Suggested by Owen Taylor. https://bugzilla.gnome.org/show_bug.cgi?id=721345
* Updated Brazilian Portuguese translationRafael Ferreira2014-01-051-104/+104
| | | | Fixes BGO#712175
* display: Don't leave focus on a window we are unmanaging when sending ↵Owen W. Taylor2013-12-241-0/+19
| | | | | | | | | | | | | | | WM_TAKE_FOCUS When we move focus elsewhere when unmanaging a window, we *need* to move the focus, so if the target is globally active, move the focus to the no-focus-window in anticipation that the focus will normally get moved to the right window when the target window responds to WM_TAKE_FOCUS. If the window doesn't respond to WM_TAKE_FOCUS, then focus will be left on the no-focus-window, but there's no way to distinguish whether the app will respond or not. https://bugzilla.gnome.org/show_bug.cgi?id=711618
* Be willing to unfocus the grab window when we are unmanaging itOwen W. Taylor2013-12-241-1/+2
| | | | | | | When we are unmanaging the grab window, we /need/ to unfocus it, so we shouldn't bail out early from meta_window_focus(). https://bugzilla.gnome.org/show_bug.cgi?id=711618
* Bump version to 3.11.33.11.3Florian Müllner2013-12-192-1/+22
| | | | Update NEWS.
* window-actor: Fix optimization in get_paint_volumeJasper St. Pierre2013-12-181-1/+5
| | | | | | | We need to clip the paint volume to the unobscured region, not the other way around... https://bugzilla.gnome.org/show_bug.cgi?id=720630
* Fix problems with focus trackingOwen W. Taylor2013-12-182-6/+27
| | | | | | | | | | | | | | When a client spontaneously focuses their window, perhaps in response to WM_TAKE_FOCUS we'll get a FocusOut/FocusIn pair with same serial. Updating display->focus_serial in response to FocusOut then was causing us to ignore FocusIn and think that the focus was not on any window. We need to distinguish this spontaneous case from the case where we set the focus ourselves - when we set the focus ourselves, we're careful to combine the SetFocus with a property change so that we know definitively what focus events we have already accounted for. https://bugzilla.gnome.org/show_bug.cgi?id=720558
* meta_window_move_resize_internal: handle border size changesOwen W. Taylor2013-12-181-0/+5
| | | | | | | | | Initial placement during meta_window_constrain() can result in changes to the borders, so we need to recompute our border sizes after constraining. This fixes incorrect window borders on initially maximized windows. https://bugzilla.gnome.org/show_bug.cgi?id=720417
* Revert "Make tile preview a compositor plugin effect"Florian Müllner2013-12-1215-216/+280
| | | | This reverts commit 21e94ed1094a31b90007089eca5174205d4861c9.
* Make tile preview a compositor plugin effectStefano Facchini2013-12-1215-280/+216
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=665758
* keybinding: Implement keybindings for moving windows between monitorsFlorian Müllner2013-12-122-0/+57
| | | | | | | | | Currently the only way to move a window to another monitor via keyboard is to start a move operation and move it manually using arrow keys. We do have all the bits of a dedicated keybinding in place already, so offer it as a more comfortable alternative. https://bugzilla.gnome.org/show_bug.cgi?id=671054
* Update Arabic translationKhaled Hosny2013-12-111-21/+21
|
* Move _NET_WM_WINDOW_OPACITY handling to the standard window-props interfaceJasper St. Pierre2013-12-098-82/+77
| | | | | | | This removes one X11 dependency that the MetaWindowActor interface has, making it easier for us to use Wayland on this one... https://bugzilla.gnome.org/show_bug.cgi?id=720106
* compositor: Remove atom_x_root_pixmapJasper St. Pierre2013-12-092-4/+1
| | | | | | It's unused https://bugzilla.gnome.org/show_bug.cgi?id=720106
* window-actor: Fix buildJasper St. Pierre2013-12-091-2/+0
| | | | This was a bad rebase...
* window-actor: Move signal handler connections to the meta-window setterJasper St. Pierre2013-12-091-5/+5
|
* window-actor: Make the meta-window property construct-onlyJasper St. Pierre2013-12-091-6/+2
| | | | | | | We don't deal with setting this property at all, and it's unlikely to come up in future settings, so just don't allow setting it at all. https://bugzilla.gnome.org/show_bug.cgi?id=678989
* window-actor: Remove meta-screen propertyJasper St. Pierre2013-12-091-19/+3
| | | | | | This can be inferred from the window. Don't allow anybody to set it. https://bugzilla.gnome.org/show_bug.cgi?id=678989
* window-actor: Remove (private) xwindow propertyJasper St. Pierre2013-12-091-44/+7
| | | | | | This should make it easier to construct a MetaWindowActor from bindings. https://bugzilla.gnome.org/show_bug.cgi?id=678989
* window: Add a simple meta_window_get_toplevel_xwindow utilityJasper St. Pierre2013-12-096-20/+14
| | | | | | | | To replace all the places where we do: window->frame ? window->frame->xwindow : window->xwindow or similar...
* window-actor: Remove outdated code pathJasper St. Pierre2013-12-091-8/+0
| | | | | | The shadow is added in the paint step, not as a separate actor, so the raise is a no-op. It also gets rid of an annoying misspelling that's driving me crazy.
* Update Chinese simplified translation甘露(Gan Lu)2013-12-071-579/+556
|
* xrandr: ignore the error if setting the primary output failsAlberto Milone2013-12-061-6/+11
| | | | | | | | | | | | | Some drivers which support RandR 1.4 may not support setting or getting the primary output, therefore mutter should trap and ignore any relevant errors. The modesetting driver exposes this problem when used in combination with the nvidia binary driver using RandR 1.4 offloading. Also use a local display variable instead of calling meta_get_display () every time.
* display: Fix checks for KeyPress/ButtonPressJasper St. Pierre2013-12-061-1/+1
|
View Lorry Controller Status