Age | Commit message (Collapse) | Author | Files | Lines |
|
Add a new frame type META_FRAME_TYPE_ATTACHED which is used for
attached modal dialogs.
The theme format version is bumped to 3.2, and attached windows
can have borders defined in a metacity-theme-3.xml as:
<window version=">= 3.2" type="attached" style_set="[name]"/>
If no style is defined for "attached", drawing will fall back
to the "border" type.
https://bugzilla.gnome.org/show_bug.cgi?id=592382
NOTE: Patch copied from mutter and adapted for metacity.
|
|
It's nice to indicate when a title is truncated with an ellipsis.
Because themes may draw a title multiple times to draw a shadow, or
may include the window icon within the title area, we can't determine
the proper ellipsization width automatically, so add an optional
attribute to the <title/> element "ellipsize_width" which, if set,
is the width to ellipsize at.
This is only enabled if a theme version of 3.1 is required.
When it's not set, we keep the old behavior of just letting the
title be clipped with a hard edge.
https://bugzilla.gnome.org/show_bug.cgi?id=591842
NOTE: Patch copied from mutter and adapted for metacity.
|
|
Sometimes you want to position something (usually the title) to be centered
with respect to the entire frame instead of centered with respect to the
individual piece currently being drawn.
This patch adds frame_x_center and frame_y_center variables that represent
the X/Y centers of the frame in the coordinate system of the piece being
drawn.
The theme version is bumped from 3.0 to 3.1 (3.0 is just the new version
system, 3.1 will have all the features we add for Mutter-2.28.)
position expressions
https://bugzilla.gnome.org/show_bug.cgi?id=591842
NOTE: Patch is copied from mutter and is adapted for metacity.
|
|
The current mechanism of metacity-theme-1.xml and metacity-theme-2.xml
is not flexible for allowing small-scale additions. With this patch
we bump the major version version once more to metacity-theme-3.xml
and add a single feature:
Any element in the DTD can have an attribute:
version="[<|<=|=>|>] MAJOR.MINOR"
And it will be ignored unless the predicate is met. (< and > should
be to be entity escaped as < and >)
This allows having alternate sections of the theme file for older and
newer version.
* Required GLib version is bumped to 2.14 so we can parse versions
with a regular expression.
* We switch internal version numbers to be "1000 * major + minor"
* We keep a stack of the maximum required version for the current portion
the XML tree so that the "cannot use versions you don't require" stricture
of the old code can be made local to a subpart of the tree.
* A version on the top metacity_theme element causes the entire file to
be ignored; this allows having one metacity-theme-3.xml for version 3.2
and newer (say) and a metacity-1.xml for everything old.
Actual new features will be added starting with 3.1 - 3.0 is just the
version="" feature.
http://bugzilla.gnome.org/show_bug.cgi?id=592503
NOTE: Patch is copied from mutter and adapted for metacity.
origin commit: https://gitlab.gnome.org/GNOME/metacity/commit/114a2048
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This commit reverts:
https://github.com/mate-desktop/marco/commit/f0541e3dfda29c26fe14c9c9117f95c49006c75c
https://github.com/mate-desktop/marco/commit/d18c2fb4acb58c408c01700682b9922de86e8b2f
And it applies an alternative to fix the deprecated functions:
gdk_screen_get_width
gdk_screen_width
gdk_screen_height
|
|
avoid deprecated:
gdk_screen_get_monitor_geometry
gdk_screen_get_monitor_at_point
|
|
|
|
|
|
default or user configured scale. Closes #335 (#336)
|
|
|
|
|
|
This legacy construct was carried over from the gtk2/gtk3 port, and
attempts to initialise MetaFrames with a GtkWindow `type` property.
This property doesn't actually exist, and will cause marco to completely
crash when running with `MARCO_DEBUG=1` for local build testing.
Signed-off-by: Ikey Doherty <[email protected]>
|
|
taken from:
https://git.gnome.org/browse/metacity/commit/?id=7ec9a6f
|
|
Taken from:
https://git.gnome.org/browse/metacity/commit/?id=3380502
|
|
taken from:
https://git.gnome.org/browse/metacity/commit/?id=02fa1e1
|
|
taken from:
https://git.gnome.org/browse/metacity/commit/?id=66d54f5
|
|
|
|
|
|
|
|
picked from upstream:
https://git.gnome.org/browse/metacity/commit/src/ui/theme-viewer.c?id=238e83a98cf014c9b1082d21541e63f102d441d6
https://git.gnome.org/browse/metacity/commit/src/ui/theme-viewer.c?id=c9099b4a90932a22c86b960c8b4dc7cd1458defe
|
|
|
|
same as done upstream:
https://git.gnome.org/browse/metacity/commit/?id=93e8c8d8b399200291965357f893fff404426eae
|
|
|
|
|
|
|
|
|
|
|
|
adapted from:
https://git.gnome.org/browse/metacity/commit/?id=e6828a3ee2cab1ec1acbdd5a444dc1cb98215a75
https://git.gnome.org/browse/metacity/commit/?id=758902aef22629943738241cea1f597b6db4b18e
https://git.gnome.org/browse/metacity/commit/?id=c6ba6dc7f458720d9f8666881f45a830580468cb
https://git.gnome.org/browse/metacity/commit/?id=68bdf1ab9de815e07f5cd75b2e1fa24ba92ae319
https://git.gnome.org/browse/metacity/commit/?id=78bbf4423f72797a05bfaddd4121d70db30de9a3
|
|
|
|
this avoids warnings like this:
Warning of Windowmanagement:Log level 16: State 4 for context 0x55988f9ad950
doesn't match state 128 set via gtk_style_context_set_state ()
|
|
|
|
|
|
|
|
|
|
taken from:
https://git.gnome.org/browse/metacity/commit/?id=5aeb6e9
|
|
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
|
|
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
|