| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=664851
|
|
|
|
|
|
|
| |
This is used to associate GtkApplication -> X window, and will
be consumed by gnome-shell.
https://bugzilla.gnome.org/show_bug.cgi?id=664851
|
| |
|
|
|
|
|
|
|
|
| |
The workspaces-only-on-primary preference changes how windows are
displayed, so listen for pref changes and update the visibility
accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=664853
|
| |
|
|
|
|
| |
Update NEWS
|
|
|
|
|
|
|
| |
Add meta_display_add_keybinding()/meta_display_remove_keybinding(),
which allow to add/remove keybindings dynamically at runtime.
https://bugzilla.gnome.org/show_bug.cgi?id=663428
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
| |
Commit d0910da036c merged the visual-bell/visual-bell-type options,
but the change turned out too disruptive for gnome-control-center /
gnome-shell, so gsettings-desktop-schemas commit a5819b2a4e9 re-added
the separate option.
|
| |
|
|
|
|
|
| |
The version has been bumped, so we can now depend on a version
which includes the new wm schemas.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Move preferences to GSettings, using mainly shared schemas from
gsettings-desktop-schemas.
Unlike GConf, GSettings support is not optional, as Gio is already
a hard dependency of GTK+.
https://bugzilla.gnome.org/show_bug.cgi?id=635378
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code here was always incorrect - we were processing damage events for
windows without having a texture. Before, this didn't matter, as
cogl_texture_get_width silently returned 0 for invalid handles. Cogl commit
4c3dadd35e4657a151025118814534d05091d4db changed this.
The fix here involves two strategies. First, we try to guard MetaTextureTower
from invalid textures. Second, we try not to go down the path that eventually
calls meta_shaped_texture_update_area by not handling damage events if we
don't have a texture for the window.
https://bugzilla.gnome.org/show_bug.cgi?id=660941
|
|
|
|
|
|
| |
gboolean is a typedef for int, so it doesn't matter too much
https://bugzilla.gnome.org/show_bug.cgi?id=660941
|
|
|
|
| |
This bumps the required GTK+ version to >= 3.3.3 .
|
|
|
|
|
|
| |
This hint reflects whether a window appears focused.
https://bugzilla.gnome.org/show_bug.cgi?id=661427
|
|
|
|
|
|
|
|
|
| |
meta_window_move_resize_frame operates much like
meta_window_move_resize, but ensures the window
and its frame (if present) will fit within the
specified dimensions.
https://bugzilla.gnome.org/show_bug.cgi?id=651899
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=662895
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=662895
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=662895
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=662895
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=662895
|
|
|
|
|
|
|
|
| |
off -Werror by default"
This reverts commit a26e72c452d98c5c2c68dcaa3d8117b86af1f9ce.
https://bugzilla.gnome.org/show_bug.cgi?id=662574
|
|
|
|
|
|
|
| |
Replace the GtkTable with a GtkGrid, replace GtkH/VBox with GtkBox
and junk a GtkHandleBox.
https://bugzilla.gnome.org/show_bug.cgi?id=662574
|
|
|
|
|
|
| |
Replace the GtkTable with a GtkGrid, replace GtkH/VBox with GtkBox
https://bugzilla.gnome.org/show_bug.cgi?id=662574
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=662574
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We never destroy the later list that's added by meta_later_add.
==4289== 16 bytes in 1 blocks are definitely lost in loss record 1,632 of 7,258
==4289== at 0x4C2640D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4289== by 0x5178D9F: standard_malloc (gmem.c:88)
==4289== by 0x5178E37: g_malloc (gmem.c:164)
==4289== by 0x51924B5: g_slice_alloc (gslice.c:842)
==4289== by 0x5194521: g_slist_insert_sorted_real (gslist.c:900)
==4289== by 0x519465A: g_slist_insert_sorted (gslist.c:957)
==4289== by 0x4EA609A: meta_later_add (util.c:876)
==4289== by 0x4E9C330: meta_screen_queue_workarea_recalc (screen.c:2640)
==4289== by 0x4E9A360: update_num_workspaces (screen.c:1646)
==4289== by 0x4E99026: meta_screen_new (screen.c:924)
==4289== by 0x4E7AB51: meta_display_open (display.c:803)
==4289== by 0x4E9168E: meta_run (main.c:552)
https://bugzilla.gnome.org/show_bug.cgi?id=642652
|
|
|
|
|
|
| |
This avoids a potentially costly allocation on every pixmap update.
https://bugzilla.gnome.org/show_bug.cgi?id=662225
|
|
|
|
|
|
|
| |
Since invisible draggable borders have been around, there isn't really a big
need for this feature
https://bugzilla.gnome.org/show_bug.cgi?id=660129
|
|
|
|
|
|
|
| |
If we are moving in snap mode (shift pressed) we don't want to tile. We must
also cancel any pending tiling if snap mode is activated during the move drag.
https://bugzilla.gnome.org/show_bug.cgi?id=662270
|
|
|
|
|
| |
We will eventually land jhbuild work to grep for warnings; for now
breaking the build is just too painful.
|
| |
|
| |
|
|
|
|
| |
Update NEWS
|
|
|
|
| |
We should still correct the coordinates for withdrawn windows.
|
|
|
|
|
|
|
|
| |
When we reparent a window to the root when we're exiting, we need to offset
the position by the invisible borders, otherwise windows will creep up and
to the left.
https://bugzilla.gnome.org/show_bug.cgi?id=660848
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=660848
|
|
|
|
|
|
|
|
|
|
|
| |
meta_window_get_current_tile_area() computes the area where the tiled window
should be based on the current pointer position but that's only meaningful
when the user is actually dragging the window.
When running the tiling constrain the pointer might be on other monitor and at
that point the window jumps to this other monitor.
https://bugzilla.gnome.org/show_bug.cgi?id=642580
|
|
|
|
|
|
|
|
|
|
|
| |
When using more than one monitor, tiled maximization can be triggered with the
pointer in one monitor while most of the window area remains in another. This
means that the maximization constraint would maximize the window into the wrong
monitor as it uses the work area size/position as target.
Fix this by using the current tile area as target size/position.
https://bugzilla.gnome.org/show_bug.cgi?id=657519
|
|
|
|
|
|
|
| |
In particular this would a cause a "flash" when showing the tile preview for
maximization on a non-primary monitor.
https://bugzilla.gnome.org/show_bug.cgi?id=662053
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
If a window had a type hint intended for override-redirect windows
like NOTIFICATION, we ended up with a window that was decorated but
with a frame type of FRAME_TYPE_LAST, causing assertion failures.
Fix this by making recalc_window_features() just call
meta_window_get_frame_type().
https://bugzilla.gnome.org/show_bug.cgi?id=599988
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=660457
|
| |
|