Age | Commit message (Collapse) | Author | Files | Lines |
|
Add tile keybinds (Fix #104, #127)
|
|
prefs: make workspace name actually change
|
|
prefs: make keybindings change notifications work with GLib >= 2.43
|
|
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.
|
|
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
|
|
now workspace names actually change on-the-fly when you change them in dconf-editor.
and this works with GLib 2.43 as well.
|
|
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
|
|
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
|
|
|
|
|
|
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.
|
|
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.
|
|
These are the minimal changes needed to make the keybinds work. Anything
else should be fixed outside handle_toggle_tiled.
|
|
Closes https://github.com/mate-desktop/marco/pull/152
|
|
merge metacity(gtk3) changes
fix warnings
clean up unused variables
replace UNUSED_VARIABLE by G_GNUC_UNUSED
|
|
GTK+ has now started using _NET_WM_STATE_HIDDEN for iconified windows.
For windows iconified at creation time, this causes metacity to set
minimize_after_placement, which then causes the window to become
minimized immediately after the first time it has been activated by
the user.
This happens because:
(1) minimize_after_placement is reset after placing the window
(2) if a window is minimized, placement is deferred
Reset minimize_after_placement unconditionally in place_window_if_needed()
to solve the issue.
Reported and tested by Daniel Drake <[email protected]>
Based on metacity commit: b0700e20b79896de7d28d2ff2bb18be324d8e19f
From: Florian Müllner <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=684741
|
|
XLib has historically used "char*" for "generic pointer" but
compliers rightly complain when casting this to a structure.
Work around this by casting to void * and letting the implicit
conversion to a structure type take effect.
Based on metacity commit: 687376bb549b3d60ba848c9d4105fe41087f3a77
From: Colin Walters <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=611644
|
|
Simplify the keymap loading logic by unifying the different
branches; in the reorganization this patch fixes a bug where when
we got a MappingKeyboard event we wouldn't update virtual modifiers
correctly.
Based on a patch by Thomas Thurman <[email protected]>
Based on metacity commit: ba2e5f7f541446931299814bafa642d09047f386
From: "Owen W. Taylor" <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=565540
|
|
* Select for XKB keyboard notification events explicitly; since GTK+
has selected for XKB events, delivery of old-school MappingNotify
events is disabled.
* Fix a bug where once a keycode was loaded for a key binding,
it would never be reassigned; we want to laod new keycodes for
all bindings that have a key symbol rather than a fixed
keycode.
[ With fixes from Owen W. Taylor <[email protected]> ]
Based on metacity commit: c262e3d65a37abedc507705cddfec72c901c321f
From: Derek Poon <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=565540
|
|
We currently allow XRaiseWindow when the same application (defined
by the window group) is focused, but the kind of old applications
that XRaiseWindow are frequently not setting the window group.
Expand the check to allow the same X client (defined by the looking
at client ID) to raise windows above the focus window.
Based on metacity commit: 632d3983fbc402432c6ceae05bea8903ad2f11c0
From: "Owen W. Taylor" <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=567528
|
|
This reverts commit 69b7a0ad9277f21ad761c84ac1bae5455a2f879e.
It has the unintended side-effect that it reverses the alt+tab
behaviour.
|
|
|
|
|
|
Taken from
https://github.com/SolusOS-discontinued/consortium/commit/b463e03f5bdeab307ceee6b969c681f29537c76d
|
|
Based on metacity commit: b235d3e78670e30a55f3f746f13003577988bed6
From: Jasper St. Pierre <[email protected]>
|
|
|
|
gdk_x11_window_lookup_for_display since 2.24
GDK_WINDOW_XID since always
gtk_widget_get_visible since 2.18
gtk_widget_set_mapped since 2.20
gdk_event_new since 2.2
gdk_x11_window_lookup_for_display since 2.24
gdk_text_property_to_utf8_list_for_display since 2.2
gtk_widget_get_realized since 2.20
gdk_visual_get_depth since 2.22
gtk_widget_get_window since 2.14
gtk_widget_set_allocation since 2.18
|
|
Based on metacity commit: 8f49828169efb43976e23dd15c6dc4d630346f50
|
|
Author: Tomaž Šolc
Based on commit: 4ecd6e49164ee027cee8dfdbb51fd8389694ff43
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=603240
|
|
gtk3 no longer has the --screen command-line argument, which
metacity was passing to zenity. Use --display (with an
explicitly-specified screen number) instead.
Author: Dan Winship
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=687938
Based on metacity commit: 8d19afdcccaec28a5512b0a707d8238b9dd4e2f3
|
|
Based on metacity commit: cd481d37ec2551e98db758ff640d02f3745259db
From: Alberts Muktupāvels <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=534752
|
|
Force to save user rect for maximized windows too, otherwise when
launching maximized application on non left monitor it will be moved
to left monitor.
Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/727928
Based on metacity commit: fbfcbc5e35e35063c8ff71b399a0bf72a31852e7
From: Alberts Muktupāvels <[email protected]>
|
|
Taken out of metacity commit: 238e83a98cf014c9b1082d21541e63f102d441d6
From: Alberts Muktupāvels <[email protected]>
|
|
Also bump minimum required glib version to 2.32.
|
|
based on metacity commit: 72d1c6a6b9a85391444bb5ff8c5de1e3aabd3fd9
From: Alberts Muktupāvels <[email protected]>
|
|
We try to exempt CSD windows from being forced fullscreen if they are
undecorated and the size of the screen; however, we also catch almost
all windows that *do* need to be forced fullscreen in this check, since
they also have decorations turned off.
Identify actual CSD windows by checking whether _GTK_FRAME_EXTENTS is set -
GTK+ will always set this on CSD windows even if they have no invisible
borders or shadows at the current time.
Based on metacity commit: 41dd72bc5dd08d7d0cb136f694a6d9a30e38b341
From: Owen W. Taylor <[email protected]>
Metacity gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=723029
|
|
Support for _GTK_FRAME_EXTENTS are based on mutter.
Based on metacity commit: e132e2a700c4b50c93eae064d8fd1769b67baf06
By: Alberts Muktupāvels <[email protected]>
|
|
Closes https://github.com/mate-desktop/marco/pull/121
Closes https://github.com/mate-desktop/marco/issues/18
|
|
Not the best solution, but the only way to fix the issue at the moment
See https://github.com/linuxmint/muffin/pull/11
Closes https://github.com/mate-desktop/marco/issues/133
|
|
|
|
The new behaviour is the animation callback function should run the
finished function once it's done with the animation.
|
|
|
|
|
|
|
|
Functions meta_window_animate_[un]minimize will handle [un]minimization animations.
Maybe this should be done in effects.c file to trigger animations based on context,
compositing, preferences etc.
|
|
Added two fields to BoxAnimationContext to handle finish callback inside
box_animation_timeout function instead of effect_free. Now the finish
function is called after the effect is finished.
|
|
|
|
Initialized at META_EFFECT_NONE. The management of this should be done by
caller functions to effect functions.
|
|
|
|
|