| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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
|
|
|
|
|
|
|
|
check for GTK+ release, not pre-release
|
|
|
|
|
|
configure.ac: removed suspicious reference to win32
|
|
|
|
|
|
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
|
|
It's been a no-op for a long time.
See https://mail.gnome.org/archives/commits-list/2011-December/msg00681.html for example.
|
|
be minimized (e.g. delete confirmation dialog, logout dialog...)
|
|
This fixes switching out of fullscreen Direct3D applications running in
Wine. See issue 166 for more details.
|
|
The theme state used to use GtkStateType, but was ported over to GtkStateFlags,
leaving behind a broken assertion that fails when using certain Metacity
themes, for example Nodoka.
https://bugzilla.gnome.org/show_bug.cgi?id=661286
https://git.gnome.org/browse/mutter/commit/?id=28deea4
https://git.gnome.org/browse/metacity/commit/?id=c9099b4
https://github.com/mate-desktop/marco/issues/205
|
|
|
|
|
|
tile preview: invalidate window before showing
|
|
Add tile keybinds (Fix #104, #127)
|
|
prefs: make workspace name actually change
|
|
prefs: make keybindings change notifications work with GLib >= 2.43
|
|
Remove information about non-existent tool run-marco.sh in HACKING
|
|
fix uninitialized data field for sending _NET_WM_SYNC_REQUEST event
|
|
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.
|
|
run-marco.sh doesn't exist so remove information about it from the
HACKING file
|
|
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
|
|
silent automake warnings about subdir warnings
Closes https://github.com/mate-desktop/marco/pull/186
|
|
from https://git.gnome.org/browse/metacity/commit/?id=5f8df557b8dbe962f19e8b641c007073665ff878
Closes https://github.com/mate-desktop/marco/pull/178
|
|
|
|
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.
|
|
This is just a copy/paste from move-to-side-{e,w} with:
s/move/tile/g
s/Move/Tile/g
.
It uses the existing handle_toggle_tiled as the backend.
|
|
|
|
|
