summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2015-09-24gtk3: fix assertion 'gtk_widget_get_realized (widget)' failedDenis Gorodnichev1-0/+2
gtk3 can use style context before widget realization
2015-09-18gtk3: draw 1px tile borderDenis Gorodnichev1-6/+9
2015-09-18Revert "Remove unused function handle_run_terminal"infirit2-0/+39
This reverts commit 437b085f123f3c019bca2481000e936ee87e7c31.
2015-09-18gtk3: unintialized variableDenis Gorodnichev1-2/+1
2015-09-16Add manual and by-pointer window placementFaidon Liambotis7-1/+103
This adds a window placement preference: the existing behavior is now called "automatic" and is the default. Two new modes are being introduced: "pointer", which means that windows are placed according to the mouse pointer position; and "manual" which means that the user must manually place the new window with the mouse or keyboard. This is a straight port from muffin, commit 3257671.
2015-09-16tile-preview: Small cleanupinfirit1-9/+1
* GDK_DISPLAY_XDISPLAY and gdk_display_get_default are in Gtk2 * Get window from GdkEvent
2015-09-16preview-widget: Small GTK_CHECK_VERSION cleanupinfirit1-10/+5
2015-09-16ui: Small cleanupsinfirit1-19/+0
* No point in checking for Gtk2 with GTK_CHECK_VERSION in Gtk2 only code * We have gdk_x11_window_lookup_for_display in Gtk2.24
2015-09-16Remove more unused functionsinfirit2-119/+0
2015-09-15Remove unused function handle_run_terminalinfirit2-39/+0
2015-09-14Remove deprecated GTK+ symbols and use accessor functionsinfirit9-289/+339
Direct struct access has been deprecated, so use the appropriate replacements to build with GSEAL enabled.
2015-09-14compositor: fix possible crash closing/destroying windowAlberts Muktupāvels3-9/+32
2015-09-14compositor: don't use invalid back_pixmapAlberts Muktupāvels1-1/+6
XCompositeNameWindowPixmap can generate BadMatch error. If this error is generated then returned pixmap is not valid. Just set back_pixmap to None in case of error.
2015-09-14bump xcomposite required version to 0.3 and simplify codeAlberts Muktupāvels4-174/+58
Version 0.3 is available more then 8 years.
2015-09-14window: load NET_WM_USER_TIME from the right windowAlberts Muktupāvels1-1/+9
On subsequent changes, if there is a NET_WM_USER_TIME_WINDOW, then read the property from that rather than from the main window. (Fix an accidental regression: the right Window was being computed but no longer passed in.) Original patch author - Owen Taylor: https://bugzilla.gnome.org/show_bug.cgi?id=585979
2015-09-14theme: Rename button_rect() to get_button_rect()Florian Müllner1-6/+6
Basically it's odd to have "button_rect" be a function with all the foo_rect GdkRectangles around - renaming to get_button_rect() will free the name for the generically named "rect" once buttons are the only movable pieces in the frame. https://bugzilla.gnome.org/show_bug.cgi?id=741917
2015-09-14ui: Refactor the default image lookupJasper St. Pierre1-20/+15
2015-09-14xprop: Don't use GDK for reading text propertiesJasper St. Pierre3-37/+24
2015-09-14Don't allow multiline window titlesWilliam Jon McCann1-0/+2
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=683056
2015-09-14Work around Xlib 64-bit "specialness"Dan Winship1-0/+14
When putting 32-bit properties into longs on 64-bit architectures, XGetWindowProperty assumes the values are supposed to be signed, and so it sign-extends values greater than 0x7fffffff. So if they *aren't* supposed to be signed, we need to chop off the high bits ourselves. (Most CARDINAL-valued properties only end up using small values anyway, so it doesn't matter, but _NET_WM_WINDOW_OPACITY uses the full range, and so was previously failing on 64-bit machines.) https://bugzilla.gnome.org/show_bug.cgi?id=605678
2015-09-14Clean up antialiasing fixesOwen W. Taylor1-24/+11
Simplify the code by noting that when we have square end-caps, the results of generic line path give the right pixel-aligned rectangle for horizontal/vertical lines. Add comments and remove some extra braces. https://bugzilla.gnome.org/show_bug.cgi?id=630426
2015-09-14Fix typoinfirit1-1/+1
2015-09-14Drop deprecated use of GTK_WIDGET_DRAWABLE, GTK_WIDGET_STATE and ↵infirit2-10/+2
gtk_widget_set_uposition
2015-09-14Drop deprecated use of gtk_signal_connect_fullinfirit1-18/+0
2015-08-31check for GTK+ release, not pre-releaseMonsta1-1/+1
2015-08-29Repaint area of deleted shadowed windows (fixes #27)bl0ckeduser1-0/+19
2015-08-20Gtk3: Fix background colorinfirit3-18/+82
Also drop the mate-desktop dark/light color functions in favour of internal ones.
2015-08-20Fix crash when struts change during grab operationOwen W. Taylor4-18/+24
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
2015-08-01window menu: make minimize item insensitive when window should notMonsta1-2/+2
be minimized (e.g. delete confirmation dialog, logout dialog...)
2015-07-31Allow programmatic minimization without MWM_FUNC_MINIMIZEStefan Dösinger1-2/+1
This fixes switching out of fullscreen Direct3D applications running in Wine. See issue 166 for more details.
2015-07-17theme: Remove outdated assertionYaakov Selkowitz2-3/+0
The theme state used to use GtkStateType, but was ported over to GtkStateFlags, leaving behind a broken assertion that fails when using certain Metacity themes, for example Nodoka. https://bugzilla.gnome.org/show_bug.cgi?id=661286 https://git.gnome.org/browse/mutter/commit/?id=28deea4 https://git.gnome.org/browse/metacity/commit/?id=c9099b4 https://github.com/mate-desktop/marco/issues/205
2015-07-11Reverting center-new-windows default to false. This is changed to match the ↵Bryan Laur1-1/+1
description of the settings. In addition, the behavior to open new windows on the top left of the screen has been consistent for over a decade. I beleive it's counter-productive to change this now.
2015-06-10Merge pull request #164 from dnk/tile_preview_glitchMartin Wimpress1-1/+2
tile preview: invalidate window before showing
2015-06-10Merge pull request #160 from micove/add-tile-keybindsMartin Wimpress6-23/+46
Add tile keybinds (Fix #104, #127)
2015-06-09Merge pull request #187 from monsta/patch-1Martin Wimpress1-1/+1
prefs: make workspace name actually change
2015-06-09Merge pull request #189 from monsta/keybindings-fixMartin Wimpress1-20/+25
prefs: make keybindings change notifications work with GLib >= 2.43
2015-06-09fix uninitialized data field for sending _NET_WM_SYNC_REQUEST eventSebastian Gerhardt1-0/+1
If this field is left uninitialized, a client may mistake Marco to support more than the single update request counter described in EWMH 1.5.
2015-04-09prefs: make keybindings change notifications work with GLib >= 2.43Monsta1-20/+25
this is achieved by using the same GSettings instance for listening and reading data. it's an additional fix for the issue with GLib >= 2.43, https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
2015-04-08prefs: make workspace name actually changemonsta1-1/+1
now workspace names actually change on-the-fly when you change them in dconf-editor. and this works with GLib 2.43 as well.
2015-04-05keybindings: pass screen name instead of number to error dialogMonsta1-7/+7
makes error dialogs on wrong command/terminal command actually work, and fixes https://github.com/mate-desktop/marco/issues/150 Closes https://github.com/mate-desktop/marco/pull/185 Closes https://github.com/mate-desktop/marco/issues/150
2015-03-15preview-widget: use correct name for missing iconmonsta1-2/+2
from https://git.gnome.org/browse/metacity/commit/?id=5f8df557b8dbe962f19e8b641c007073665ff878 Closes https://github.com/mate-desktop/marco/pull/178
2015-02-25prefs: first connect to settings, then read them.Monsta1-7/+7
fixes the issue with GLib >= 2.43, https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 Closes https://github.com/mate-desktop/marco/pull/174
2015-01-23Possible keybinding to switch to previous workspace.Robert David7-1/+33
Disabled at default.
2015-01-14check compositor statusDenis Gorodnichev5-30/+34
2015-01-14show tile preview with external compositorDenis Gorodnichev3-10/+6
2015-01-14tile preview: invalidate window before showingDenis Gorodnichev1-1/+2
2015-01-01BugFix: Can't retile to a different corner with keybindings.Miguel A. Colón Vélez1-1/+1
has_maximize_func implies window->has_resize_func !window->fullscreen window->has_resize_func implies (window->size_hints.min_width < window->size_hints.max_width) || (window->size_hints.min_height < window->size_hints.max_height) A tiled window implies that it could be tiled. A maximized window implies that it could be tiled. . Therefore simplify the if and add window->shaded to make it equivalent to the macro but allowing to tile already maximized/tiled windows. . If this commit causes a regression it probably means that a call to meta_window_recalc_features is missing. . This bug already existed but can only be triggered by the new keybindings.
2015-01-01BugFix: Can't unmaximize a tiled window.Miguel A. Colón Vélez1-15/+1
The removed code did not allow tiled windows to be unmaximized. The code was trying to retile a tiled window when it was asked to unmaximize it. The only thing it did was turn a maximized window into a tiled window but that is not the normal expected behaviour of unmaximization. . I also reset window->tile_mode to ensure we always unmaximize correctly. Some duplicate code was also removed. . This bug affects tiling with: - tile-to-side-w - tile-to-side-e - Mouse dragging to the west corner - Mouse dragging to the east corner . Therefore it's an old bug unrelated to the new keybindings.
2015-01-01Update handle_toggle_tiled.Miguel A. Colón Vélez1-7/+19
These are the minimal changes needed to make the keybinds work. Anything else should be fixed outside handle_toggle_tiled.
2015-01-01Add the tile-to-side options to the appropiate files.Miguel A. Colón Vélez4-0/+25
This is just a copy/paste from move-to-side-{e,w} with: s/move/tile/g s/Move/Tile/g . It uses the existing handle_toggle_tiled as the backend.