summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* fix problems with focus trackinggnome-3-28Owen W. Taylor2018-09-102-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
* display: ensure that we ignore our own focus events for focus predictionsAlberts Muktupāvels2018-09-102-15/+46
| | | | | | | | | | | | | | | | | | | | When we set the input focus, we first set the predicted window, and then try to process focus events. But as FocusOut on the existing window comes before FocusIn on the new window, we'll see the focus out on the old window and think the focus is going to nothing, which makes metacity think the prediction failed. Fix this by making sure that we ignore focus window changes of our own cause when updating the focus window field, by ignoring all focus events that have a serial the same as the focus request or lower. Note that if metacity doens't make any requests after the focus request, this could be racy, as another client could steal the focus, but metacity would ignore it as the serial was the same. Bump the serial by making a dummy ChangeProperty request to a metactiy-controlled window in this case. Based on mutter commit: https://gitlab.gnome.org/GNOME/mutter/commit/7fdfbad6d495ede1632588e528801443846e5f6d
* Update zh_CN translationDz Chen2018-03-241-1078/+1222
|
* bump version to 3.28.0, update NEWS3.28.0Alberts Muktupāvels2018-03-112-1/+8
|
* frames: ignore gdk_window_process_all_updates deprecation warningsAlberts Muktupāvels2018-03-111-2/+10
|
* metaaccellabel: avoid implicit conversion warningAlberts Muktupāvels2018-03-111-1/+1
| | | | | warning: implicit conversion from ‘gfloat {aka float}’ to ‘double’ to match other operand of binary expression [-Wdouble-promotion]
* require gtk+ 3.22.0Alberts Muktupāvels2018-03-116-95/+1
|
* avoid deprecated gdk error trap functionsAlberts Muktupāvels2018-03-114-11/+34
|
* build: enable subdir-objectsAlberts Muktupāvels2018-03-111-1/+1
|
* frames: avoid implicit conversion warningsAlberts Muktupāvels2018-03-111-4/+4
| | | | | warning: implicit conversion from ‘float’ to ‘double’ to match other operand of binary expression [-Wdouble-promotion]
* libmetacity: avoid implicit conversion warningsAlberts Muktupāvels2018-03-111-4/+4
| | | | | warning: implicit conversion from ‘float’ to ‘double’ to match other operand of binary expression [-Wdouble-promotion]
* Update Croatian translationgogo2018-03-101-3222/+1100
|
* Updated Danish translationJoe Hansen2018-03-031-1235/+10
|
* window: make docks and spashscreens appear focusedAlberts Muktupāvels2018-02-221-1/+11
| | | | | | | | | Set the NET_WM_STATE_FOCUSED property on windows of type dock or spashscreen so that they don't get the state GTK_STATE_FLAG_BACKDROP set by default. Based on xfwm4 commit: https://git.xfce.org/xfce/xfwm4/commit/?id=0feb29e78bb3
* update git.mk to latest versionAlberts Muktupāvels2018-02-222-1/+43
|
* Update Esperanto translationKristjan SCHMIDT2017-12-231-1015/+1022
|
* Updated Danish translationAsk Hjorth Larsen2017-11-111-488/+513
|
* compositor: fix missing shadow from some windowsAlberts Muktupāvels2017-10-201-7/+15
| | | | | | | If window is not client side decorated then we should add shadow also when using GTK+ theme. https://bugzilla.gnome.org/show_bug.cgi?id=789251
* window: don't manage InputOnly windowsAlberts Muktupāvels2017-10-171-2/+14
|
* bump version to 3.26.0, update NEWS3.26.0Alberts Muktupāvels2017-10-022-2/+9
|
* theme-viewer: unmark string from translationPiotr Drąg2017-10-021-1/+1
|
* theme-viewer: move combo boxes to sidebarAlberts Muktupāvels2017-10-022-264/+292
|
* Update Swedish translationAnders Jonsson2017-10-021-51/+51
|
* data: remove X-GNOME-BugzillaAlberts Muktupāvels2017-09-301-3/+0
|
* stack-tracker: keep override redirect windows on topRui Matos2017-09-301-0/+37
| | | | | https://git.gnome.org/browse/mutter/commit/?id=e3d5bc07 https://bugzilla.gnome.org/show_bug.cgi?id=780485
* screen: unset timeout ID after removalFlorian Müllner2017-09-301-0/+1
| | | | | | | Otherwise we may try to remove the now invalid ID again, resulting in a warning. https://bugzilla.gnome.org/show_bug.cgi?id=788292
* ui: fix memory leak when changing themeAlberts Muktupāvels2017-09-301-2/+3
| | | | | | g_set_object increments reference count of new_object. https://bugzilla.gnome.org/show_bug.cgi?id=788078
* main: do not call g_printerr in a signal handlerAlberts Muktupāvels2017-09-291-2/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=603510
* window: fix build warningsAlberts Muktupāvels2017-09-291-4/+12
| | | | this statement may fall through [-Wimplicit-fallthrough=]
* window: minor fixes from mutter e3d59832 commitAlberts Muktupāvels2017-09-291-11/+24
|
* Update Hungarian translationBalázs Úr2017-09-051-100/+103
|
* Updated Serbian translationМирослав Николић2017-08-122-662/+536
|
* screen: fix build warningAlberts Muktupāvels2017-08-071-9/+5
|
* keybindings: use meta_error_trap_pop in grab_keyboardAlberts Muktupāvels2017-07-211-1/+1
| | | | | We are not using return value from meta_error_trap_pop_with_return if keyboard grab has failed, replace it with meta_error_trap_pop.
* edge-resistance: fix use of uninitialized memoryColin Walters2017-07-211-1/+1
| | | | g_new bad, g_new0 good.
* Fix crash when struts change during grab operationOwen W. Taylor2017-07-214-19/+27
| | | | | | | | | | | | | | | | | | | | | | | | Since meta_workspace_invalidate_work_area() frees the edges workspace->screen_edges and workspace->monitor_edges, we must clean up our cached edge resistance data when the invalidate_work_area() is called on the active workspace, or when the workspace changes. Make the computation of the edge resistance data lazy so that it will be recomputed the next time we try to access it. meta_display_compute_resistance_and_snapping_edges() is made private to edge-resistance.c Invaliding the data when active workspace changes also will improve correctness for edge resistance when the current workspace changes during a grab operation. (Even with this fix we still don't try to handle window positions changing during a grab operation; that can't cause a crash since, unlike screen and monitor edges, the window edges are freshly allocated, it will just cause slight oddness in that corner case.) Root cause tracked down due to much effort by Jon Nettleton. https://bugzilla.gnome.org/show_bug.cgi?id=608800 (Mutter) https://bugzilla.gnome.org/show_bug.cgi?id=603632 (Metacity)
* Accept an empty string as well as "disabled" for keybindingsOwen W. Taylor2017-07-211-2/+2
| | | | | | | | Treat the empty string the same as "disabled" for GConf keybinding keys. gnome-keybinding-properties was changed to write disabled keys as the empty string a year or so ago. https://bugzilla.gnome.org/show_bug.cgi?id=559816
* libmetacity: set a clip region for titleAlberts Muktupāvels2017-07-211-0/+11
|
* libmetacity: add space between buttons and titleAlberts Muktupāvels2017-07-201-6/+2
|
* libmetacity: properly calculate available space for buttonsAlberts Muktupāvels2017-07-202-5/+11
|
* libmetacity: fix copy/paste errorsAlberts Muktupāvels2017-07-182-4/+4
|
* display: remove meta_display_screen_for_rootAlberts Muktupāvels2017-07-042-13/+1
|
* core: simplify meta_core_get_workspace_name_with_indexAlberts Muktupāvels2017-07-043-14/+3
|
* xrender: simplify process_property_notifyAlberts Muktupāvels2017-07-041-16/+13
|
* keybindings: fix shortcuts regressionAlberts Muktupāvels2017-07-041-5/+1
| | | | | | | | Commit b9cfaa8803fa019b3a1502b067802f2434b6e737 removed meta_display_screen_for_xwindow function. It was supposed to be replaced with display->screen... https://bugzilla.gnome.org/show_bug.cgi?id=784500
* workspace: reformatAlberts Muktupāvels2017-07-031-38/+42
|
* workspace: fix a build warningAlberts Muktupāvels2017-07-031-0/+3
|
* workspace: remove unneeded function prototypesAlberts Muktupāvels2017-07-031-5/+1
|
* vulkan: fix a build warningAlberts Muktupāvels2017-07-031-0/+2
|
* window: clear frame_bounds region earlierAlberts Muktupāvels2017-07-021-6/+6
| | | | | Clear region before calling meta_compositor_sync_window_geometry function, otherwise compositor will use cached region.
View Lorry Controller Status