| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Having keybindings for side-by-side tiling has been requested for
a long time, so add this support now.
https://bugzilla.gnome.org/show_bug.cgi?id=648700
Based on mutter commit:
https://git.gnome.org/browse/mutter/commit/?id=34f6ffd1ad0d3b7369120a9802d84517748fe887
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than defining keybindings in static arrays generated at compile
time, store them in a hash table initialized in meta_display_init_keys()
and filled in init_builtin_keybindings().
This is a prerequisite for allowing to add/remove keybindings at runtime.
https://bugzilla.gnome.org/show_bug.cgi?id=663428
Based on mutter, mostly on this commit by Florian:
https://git.gnome.org/browse/mutter/commit/?id=d42a2a3c2741b8b44b48f83eb79a82fb4fcd5bbd
|
| |
|
| |
|
|
|
|
|
|
| |
If windows are not resizable then invisible border is set to 0.
This is problem with GTK+ themes because border (box-shadow) is in
invisible area.
|
|
|
|
|
|
|
|
| |
Since the frame window size that meta_window_move_resize() uses depends
on whether the window has horizontal/vertical resize functionality, we
need to update this flag before we resize the window.
https://bugzilla.gnome.org/show_bug.cgi?id=659854
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
There is no good reason to do so, besides a nice way to check whether
a particular button is enabled. However there are legitimate reasons
for overdrawing like box-shadows or outlines, so remove the clip.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=745108
|
| |
|
|
|
|
|
|
| |
Compositing manager is enabled by default since commit
317c52fdb82384762a18ec5a3a6c0165dda5d360, but default value was
not updated. Do it now.
|
|
|
|
|
| |
We need to update style info when changing compositing manager
setting to get correct data for GTK+ theme.
|
|
|
|
|
| |
Based on mutter commit:
https://git.gnome.org/browse/mutter/commit/?id=c2a9ccb7e2e0f7dc37866099a5e5a4a5727c679b
|
|
|
|
|
|
| |
While this works fine with metacity it will not work in compiz
gtk-window-decorator as this function will return only default
value - NULL.
|
| |
|
|
|
|
|
| |
And use it as invisible area for resizing if compositing manager
is running otherwise use as extra size for visible border.
|
|
|
|
| |
... if running without compositing manager.
|
|
|
|
| |
... when running without compositing manager.
|
|
|
|
|
| |
GTK+ theme might use this area to paint box-shadow. Also use
CAIRO_CONTENT_COLOR_ALPHA for cairo surfaces.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All geometry/drawing information is now picked up from the GTK+ theme,
so replace the remaining bits (hide_buttons + title_scale) with
hardcoded values from the default Adwaita theme.
If there is a need to theme those constants again in the future,
we should make them available from GTK+ where they are available
for client-side decorations as well. They certainly don't justify
maintaining support for a complex theme format.
Based on mutter commit:
https://git.gnome.org/browse/mutter/commit/?id=d5e6177900f5cdf90bb3ba86603d6b6ff0a919f7
|
|
|
|
|
|
|
|
|
| |
With geometry information picked up from GTK+, we need to queue a
resize on GTK+ theme changes to correctly update to the new geometry.
https://bugzilla.gnome.org/show_bug.cgi?id=741917
NOTE: Updated for metacity.
|
|
|
|
| |
Theme name == NULL - use current GTK+ theme.
|
|
|
|
| |
... b0fb6df3ab09995c4d35dfb49f30aeb711239806
|
|
|
|
|
| |
Based on mutter commit:
https://git.gnome.org/browse/mutter/commit/?id=274ea76eea6e97be01a723122c0774e7e961bff2
|
| |
|
|
|
|
|
|
| |
Based on mutter commits:
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=746898
|
|
|
|
|
| |
Based on mutter commit:
https://git.gnome.org/browse/mutter/commit/?id=6e47f0e846968ebf7e9637f09af17bbf3cd36fca
|
| |
|
|
|
|
| |
This enables CSD for X11 clients (in XWayland and in X11)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
... to differentiate PangoLayout from MetaFrameLayout.
https://bugzilla.gnome.org/show_bug.cgi?id=741917
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GTK+ doesn't deal with different frame types for its client-side
decorations - it just treats dialogs the same as normal windows
and ignores the odder frame types like UTILITY and MENU. That's
fine as those have largely gone out of fashion anyway, but it's a
different case for the WM - we still have to support them somehow.
For now, just apply the existing title_scale factor to the geometry
information picked up from the theme in addition to the title font.
If it turns out that there's demand for something more sophisticated,
we can still consider adding wm-only style information to the GTK+
theme.
https://bugzilla.gnome.org/show_bug.cgi?id=741917
|
|
|
|
|
|
|
|
|
|
|
| |
We now have everything in place to pick up geometry and drawing
information from GTK+ rather than the metacity theme, so do just
that; the metacity theme is now only used for some constants
(title_scale, hide_buttons, ...), which we will replace soon.
https://bugzilla.gnome.org/show_bug.cgi?id=741917
NOTE: Updated for metacity.
|
|
|
|
|
|
|
|
|
|
| |
We want to eventually pick up all theme information from GTK+ instead
of our own theme format; to prepare for this, add another helper method
to fill in geometry information from the GTK+ theme.
https://bugzilla.gnome.org/show_bug.cgi?id=741917
NOTE: Updated for metacity.
|
|
|
|
|
|
|
|
| |
GTK+ expresses the window state as style classes and widget state for
client-side decorations. Add a helper method to translate our own frame
state to the corresponding changes to the style context hierarchy.
https://bugzilla.gnome.org/show_bug.cgi?id=741917
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sounds obvious, doesn't it?
After this change when titlebar-uses-system-font is set, the "system
font" used will not be a generic one, but match what GTK+ uses in
client-side decorations.
https://bugzilla.gnome.org/show_bug.cgi?id=741917
NOTE: Updated for metacity.
|
| |
|