Age | Commit message (Collapse) | Author | Files | Lines |
|
https://gitlab.gnome.org/GNOME/metacity/commit/1fafd279006ece8cf664fd777143cdfafbefad6d
window: handle legacy fullscreen requests
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
Bug 781946 - Non-native decorated windows stuck maximised on secondary screen with Marco/Metacity
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=656619
upstream commit:
https://gitlab.gnome.org/GNOME/metacity/commit/4674358f
|
|
MetaFrameBorders leaked when orig_borders != NULL and
window->fullscreen == TRUE
https://bugzilla.gnome.org/show_bug.cgi?id=679153
upstream commit:
https://gitlab.gnome.org/GNOME/metacity/commit/7e7f25f4
|
|
upstream commit:
https://gitlab.gnome.org/GNOME/metacity/commit/67ddadf3
|
|
There were actually *two* MetaFrameGeometry structs: one in theme-private.h,
one in frame.h. The latter public struct was populated by a mix of (void*)
casting and int pointers, usually pulling directly from the data in the private
struct.
Remove the public struct, replace it with MetaFrameBorders and scrap all
the pointer hacks to populate it, instead relying on both structs being used
in common code.
This commit should be relatively straightforward, and it should not do any
tricky logic at all, just a sophisticated find and replace.
https://bugzilla.gnome.org/show_bug.cgi?id=644930
upstream commit: https://gitlab.gnome.org/GNOME/metacity/commit/72224a165
NOTE: Patch copied from metacity and adapted for marco.
|
|
|
|
Add a preference /apps/mutter/general/attach_modal_dialogs. When
true, instead of having independent titlebars, modal dialogs appear
attached to the titlebar of the parent window and are moved
together with the parent window.
https://bugzilla.gnome.org/show_bug.cgi?id=612726
NOTE: Patch copied from mutter and adapted for metacity.
|
|
|
|
|
|
|
|
Use that flag to retain the correct window size when performing other
operations. Reset when re-tiling.
|
|
Determine whether the user is initiating a resize action on a tiled
window. If the user is trying to grab the window for resizing
horizontally from the edge that's farther away from the screen edge,
allow the resize to occur. Otherwise maintain the current tile geometry.
Also modified the window hints to allow resizing from the window menu.
Fixes #250
|
|
ported from
https://git.gnome.org/browse/metacity/commit/?id=8f699b71bd7e5581ec2f2804ea9650597618dfe1
|
|
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
|
|
Taken from
https://github.com/SolusOS-discontinued/consortium/commit/b463e03f5bdeab307ceee6b969c681f29537c76d
|
|
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
|
|
Just run:
$ find -name '*.c' -print0 | xargs -r0 sed -e 's/[[:blank:]]\+$//' -i
$ find -name '*.h' -print0 | xargs -r0 sed -e 's/[[:blank:]]\+$//' -i
|
|
|
|
If you maximize a CSD window on a monitor without struts, it ends up
taking the whole monitor size, but it doesn't mean that the application
wants to fullscreen.
Gnome Bug:
https://bugzilla.gnome.org/show_bug.cgi?id=708718
Gnome Commit:
https://git.gnome.org/browse/mutter/commit/src/core/constraints.c?id=4eeeb1557a3a0caff6ef1debd92aeb541ae1b556
|
|
Patch by Florian Müllner for Metacity
https://bugzilla.gnome.org/show_bug.cgi?id=607694
When dragging a window over a screen edge and dropping it there,
maximize it vertically and scale it horizontally to cover the
corresponding half of the current monitor.
Whenever a "hot area" which triggers this behavior is entered, an
indication of window's target size is displayed after a short delay
to avoid distraction when moving a window between monitors.
|
|
|
|
|