- Dec 21, 2017
-
-
Dmitry Shachnev authored
-
Dmitry Shachnev authored
-
- Oct 02, 2017
-
-
Alberts Muktupāvels authored
-
Piotr Drąg authored
-
Alberts Muktupāvels authored
-
Anders Jonsson authored
-
- Sep 30, 2017
- Sep 29, 2017
-
-
Otherwise we may try to remove the now invalid ID again, resulting in a warning. https://bugzilla.gnome.org/show_bug.cgi?id=788292
-
Alberts Muktupāvels authored
g_set_object increments reference count of new_object. https://bugzilla.gnome.org/show_bug.cgi?id=788078
-
-
Alberts Muktupāvels authored
this statement may fall through [-Wimplicit-fallthrough=]
-
Alberts Muktupāvels authored
-
- Sep 05, 2017
-
-
Balázs Úr authored
-
- Aug 12, 2017
-
-
Мирослав Николић authored
-
- Aug 07, 2017
-
-
Alberts Muktupāvels authored
-
- Jul 21, 2017
-
-
Alberts Muktupāvels authored
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.
-
g_new bad, g_new0 good.
-
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)
-
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
-
- Jul 20, 2017
-
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
- Jul 18, 2017
-
-
Alberts Muktupāvels authored
-
- Jul 04, 2017
-
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
Commit b9cfaa88 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
-
- Jul 03, 2017
-
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
- Jul 02, 2017
-
-
Alberts Muktupāvels authored
Clear region before calling meta_compositor_sync_window_geometry function, otherwise compositor will use cached region.
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
- Jun 28, 2017
-
-
Alberts Muktupāvels authored
Doing this on the actual resize requests makes more sense than handling it as a window-manager imposed constraints, so move the code accordingly. Adapted from mutter patch by Florian Müllner: https://git.gnome.org/browse/mutter/commit/?id=fba022cc06b8c7e80ef36f48d6577a251384cc4b https://bugzilla.gnome.org/show_bug.cgi?id=781946
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-
Alberts Muktupāvels authored
-