Age | Commit message (Collapse) | Author | Files | Lines |
|
partially taken from:
https://git.gnome.org/browse/metacity/commit/?id=51b9e57
|
|
taken from:
https://git.gnome.org/browse/metacity/commit/?id=1f2ea05
|
|
taken from:
https://git.gnome.org/browse/metacity/commit/?id=7a5c50c
|
|
taken from:
https://git.gnome.org/browse/metacity/commit/?id=e00996a
|
|
gtk_style_context_get_background_color
partially taken from:
https://git.gnome.org/browse/metacity/commit/?id=33ad43f
|
|
partially taken from:
https://git.gnome.org/browse/metacity/commit/?id=542a2b4
|
|
Add GTK_STYLE_CLASS_BACKGROUND class to context, so we have correct colors from the GTK+ theme instead of white text over black background.
|
|
- this fixes the bg/fg color mismatch between normal tooltips,
which are styleable in themes
taken from:
https://git.gnome.org/browse/metacity/commit/?id=3aa71b7
|
|
This reverts commit 567890a8a1884247de29e9f97cf9cd8110247c04, reversing
changes made to a65a66d49bd0d6ec6c94b8e3ecd551cb570cec95.
|
|
This fix random bug when applications without reason opens in
fullscreen mode.
|
|
|
|
ported from
https://git.gnome.org/browse/metacity/commit/?id=8f699b71bd7e5581ec2f2804ea9650597618dfe1
|
|
fixes https://github.com/mate-desktop/marco/issues/200
ported to Marco from https://github.com/GNOME/metacity/commit/f25b7760b7430b674afdb4de1e2072cd99ea3fbc
|
|
|
|
This reverts commit b53fb913abe7da1e8d56bd50151f673c90cf121d.
Fixes https://github.com/mate-desktop/marco/issues/226
|
|
closes https://github.com/mate-desktop/marco/issues/90
|
|
to better match it.
This reverts commit 8ca77c72992ab6c1ccf7191b1b38d967b2d68348.
|
|
gtk3: fix assertion 'gtk_widget_get_realized (widget)' failed
|
|
gtk3: unintialized variable
|
|
Reverting center-new-windows default to false.
|
|
Possible keybinding to switch to previous workspace.
|
|
gtk3 can use style context before widget realization
|
|
|
|
This reverts commit 437b085f123f3c019bca2481000e936ee87e7c31.
|
|
|
|
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.
|
|
* GDK_DISPLAY_XDISPLAY and gdk_display_get_default are in Gtk2
* Get window from GdkEvent
|
|
|
|
* 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
|
|
|
|
|
|
Direct struct access has been deprecated, so use the appropriate
replacements to build with GSEAL enabled.
|
|
|
|
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.
|
|
Version 0.3 is available more then 8 years.
|
|
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
|
|
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
|
|
|
|
|
|
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=683056
|
|
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
|
|
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
|
|
|
|
gtk_widget_set_uposition
|
|
|
|
|
|
|
|
Also drop the mate-desktop dark/light color functions in favour
of internal ones.
|
|
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
|
|
be minimized (e.g. delete confirmation dialog, logout dialog...)
|