summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* use gtk+ theme implwip/no-reparentJasper St. Pierre2014-02-2027-17790/+221
|
* Remove tabpopup and friendsJasper St. Pierre2014-02-2012-2368/+5
| | | | These are unused in gnome-shell, and add complexity. Remove them.
* Bump version to 3.11.903.11.90Florian Müllner2014-02-192-1/+17
| | | | Update NEWS.
* Make tile preview a compositor plugin effectStefano Facchini2014-02-1915-276/+216
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=665758
* Revert "compositor: Delay meta_compositor_add_window until the first show"Jasper St. Pierre2014-02-192-12/+21
| | | | This reverts commit e3a93db712aea3c138b287786e4cd8d3ce0968d8.
* default: Use a consistent rand() for monitor backgroundsJasper St. Pierre2014-02-171-3/+6
| | | | g_random_int() is seeded with /dev/urandom, so it's not consistent.
* default: Don't wait to show the stageJasper St. Pierre2014-02-171-18/+1
| | | | We can show it immediately now...
* Fix regression in mutter translationsGiovanni Campagna2014-02-1726-25/+63
| | | | | | | | | | | | | Switching meta/util.h to gi18n.h was wrong, mutter is a library and needs gi18n-lib.h, but that cannot be included from a public header (since it depends on config.h or command line options), so split util.h into a public and a private part. https://bugzilla.gnome.org/show_bug.cgi?id=707897 Conflicts: src/compositor/compositor.c src/meta/util.h
* util: fix warnings when compiling gnome-shell-waylandGiovanni Campagna2014-02-171-4/+1
| | | | | | | Replace our version of the gettext macros with those in glib, so that they don't conflict with gnome-shell. https://bugzilla.gnome.org/show_bug.cgi?id=707851
* Move position-changed / size-changed signals to the MetaWindowJasper St. Pierre2014-02-142-35/+42
| | | | | | They fit more appropriately over here... https://bugzilla.gnome.org/show_bug.cgi?id=720631
* compositor: Delay meta_compositor_add_window until the first showJasper St. Pierre2014-02-142-21/+12
| | | | | | | | | | | In order for the compositor to properly determine whether a client is an X11 client or not, we need to wait until XWayland calls set_window_id to mark the surface as an XWayland client. To prevent the compositor from getting tripped up over this, make sure that the window has been fully initialized by the time we call meta_compositor_add_window. https://bugzilla.gnome.org/show_bug.cgi?id=720631
* Always map the client and frame windowsJasper St. Pierre2014-02-149-253/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Traditionally, WMs unmap windows when minimizing them, and map them when restoring them or wanting to show them for other reasons, like upon creation. However, as metacity morphed into mutter, we optionally chose to keep windows mapped for the lifetime of the window under the user option "live-window-previews", which makes the code keep windows mapped so it can show window preview for minimized windows in other places, like Alt-Tab and Expose. I removed this preference two years ago mechanically, by removing all the if statements, but never went through and cleaned up the code so that windows are simply mapped for the lifetime of the window -- the "architecture" of the old code that maps and unmaps on show/hide was still there. Remove this now. The one case we still need to be careful of is shaded windows, in which we do still unmap the client window. In the future, we might want to show previews of shaded windows in the overview and Alt-Tab. In that we'd also keep shaded windows mapped, and could remove all unmap logic, but we'd need a more complex method of showing the shaded titlebar, such as using a different actor. At the same time, simplify the compositor interface by removing meta_compositor_window_[un]mapped API, and instead adding/removing the window on-demand. https://bugzilla.gnome.org/show_bug.cgi?id=720631
* window: Centralize WM_STATE managementJasper St. Pierre2014-02-141-12/+16
|
* idle-monitor: avoid XSyncBadAlarm X errorRyan Lortie2014-02-141-1/+1
| | | | | | | | If we fail to find the IDLETIME counter, then the alarm variable will be uninitialised. Most code paths are careful to check this before submitting XSync calls, but there is one check missing. https://bugzilla.gnome.org/show_bug.cgi?id=724364
* Updated Ukrainian translationDaniel Korostil2014-02-131-581/+537
|
* window: don't set _NET_WM_FULLSCREEN_MONITORS to bogus valuesGiovanni Campagna2014-02-132-17/+31
| | | | | | | | | | | | | | | Prior to the DisplayConfig merge, we would set _NET_WM_FULLSCREEN_MONITORS to (unsigned)-1 when unset. After that, we would have invalid reads inside meta_screen_monitor_index_to_xinerama_index() (called with -1). The way I read the specification, the proper way to indicate that the window is back to fullscreen on all monitors is to remove the property, so do that. Also, add an assertion that meta_screne_monitor_index_to_xinerama_index() is doing the right thing. https://bugzilla.gnome.org/show_bug.cgi?id=724258
* window: fix invalid read in computing the input shapeGiovanni Campagna2014-02-131-3/+3
| | | | | | | If we are reported only one rectangle in the input shape, we should not try to read more. https://bugzilla.gnome.org/show_bug.cgi?id=724257
* Updated Norwegian bokmål translationKjartan Maraas2014-02-101-228/+235
|
* default: Make the map animation more friendlyJasper St. Pierre2014-02-091-5/+5
|
* autogen.sh: use #!/bin/sh instead of #!/bin/bashRyan Lortie2014-02-091-1/+1
| | | | | | We don't have any bashisms in this file, so we may as well use sh. https://bugzilla.gnome.org/show_bug.cgi?id=722530
* Disable clutter's high dpi scalingAdel Gadllah2014-02-091-0/+8
| | | | | | | mutter needs some work to work with high dpi scaling so disable the scaling until that is fixed. https://bugzilla.gnome.org/show_bug.cgi?id=723931
* Updated Czech translationMarek Černocký2014-02-091-233/+240
|
* Update Arabic translationKhaled Hosny2014-02-061-232/+239
|
* shaped-texture: Fix unused variable warningRico Tzschichholz2014-02-051-1/+0
|
* shaped-texture: Make sure to set the texture tower's textureJasper St. Pierre2014-02-051-3/+8
| | | | This was part of the Wayland branch that I forgot to cherry-pick properly.
* shaped-texture: Move unobscured_region processing hereJasper St. Pierre2014-02-054-67/+101
| | | | | | | | | We want to remove a bunch of auxilliary duties from the MetaWindowActor and MetaSurfaceActor, including some details of how culling is done. Move the unobscured region culling code to the MetaShapedTexture, which helps the actor become "more independent". https://bugzilla.gnome.org/show_bug.cgi?id=720631
* cullable: Reset the culling state instead of skipping the traversalJasper St. Pierre2014-02-055-39/+40
| | | | | | | | | | | When we traversed down to reset the culling state, previously we would just skip any actors that wanted culling. In order to properly reset the unobscured_region before painting, we need to traverse down to these places as well. Do this by calling cull_out with NULL regions for both arguments, and adapt existing cull_out implementations to match. https://bugzilla.gnome.org/show_bug.cgi?id=720631
* window-actor: Move all buffer management and damage correction hereJasper St. Pierre2014-02-055-52/+70
| | | | | We want ShapedTexture to be a dumb actor that knows how to pick/paint fairly easily, without any "platform knowledge", so to say...
* window-actor: Clean up whitespaceJasper St. Pierre2014-02-051-6/+2
|
* shaped-texture: Clean up code flow a bitJasper St. Pierre2014-02-051-6/+5
| | | | This is easier for me to read.
* updated kn.poShankar Prasad2014-02-051-1835/+177
|
* xrandr: Use specified output property name for backlight controlRobert Ancell2014-02-052-4/+4
| | | | | | | | | | | | Backlight controls are set using the "BACKLIGHT" XRANDR output property. This should be "Backlight" according to the XRANDR spec [1]. Some drivers (Intel) export both properties and some only the specified property (nvidia). Users of drivers that only export the specified property cannot change their backlight using XRANDR. [1] http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt section 9.1 https://bugzilla.gnome.org/show_bug.cgi?id=723606
* Bump version to 3.11.53.11.5Florian Müllner2014-02-042-1/+16
| | | | Update NEWS.
* default plugin: Fix workspace switch type errorJonas Ådahl2014-02-031-1/+3
| | | | | | Signed-off-by: Jonas Ådahl <jadahl@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=723563
* compositor: Fix crash on startupJasper St. Pierre2014-02-021-0/+2
| | | | | A bad rebase in 757674a9d69881b1bd483a8c5b77a345ebb46fc6 accidentally removed the call to meta_plugin_manager_new().
* monitorManager: Fix logic bug in make_logical_configAdel Gadllah2014-02-021-1/+1
| | | | | | | | The code that prevents the creation of multiple MonitorInfos for clones wasn't working due to using the wrong index when getting the already created info so fix that to use the correct one. https://bugzilla.gnome.org/show_bug.cgi?id=710610
* window_actor: Remove the frame_messages timeout in destroyAdel Gadllah2014-02-021-0/+6
| | | | | | Otherwise it might fire off later and cause a crash. https://bugzilla.gnome.org/show_bug.cgi?id=723468
* window: fix coerced valueMarek Ch2014-02-021-1/+1
| | | | (int) 0.5 = 0, so there always was 0 instead of 50%
* Updated Traditional Chinese translation(Hong Kong and Taiwan)Chao-Hsiung Liao2014-02-022-56/+76
|
* window-actor: Fix buildJasper St. Pierre2014-02-011-1/+1
| | | | | This was renamed to detach_x11_pixmap on the Wayland branch, and was blindly cherry-picked onto master.
* compositor: Remove pending_input_regionJasper St. Pierre2014-01-312-54/+20
| | | | | | | | Ever since the change to create the output window synchronously at startup, there hasn't been any time where somebody could set a stage region the output window was ready, so this was effectively dead code. https://bugzilla.gnome.org/show_bug.cgi?id=720631
* window-actor: Remove old unused APIsJasper St. Pierre2014-01-313-57/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=720631
* window-actor: Flip set_redirected aroundJasper St. Pierre2014-01-313-17/+17
| | | | | | | I know it's confusing with the triple negative, but unredirected is how we track it elsewhere: we have an 'unredirected' flag, and 'should_unredirect'. https://bugzilla.gnome.org/show_bug.cgi?id=720631
* compositor: Simplify the unredirected window management codeJasper St. Pierre2014-01-313-32/+32
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=720631
* window-actor: Simplify the unredirected check in cull_outJasper St. Pierre2014-01-311-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=720631
* screen: Make the guard window an InputOnly windowJasper St. Pierre2014-01-311-5/+4
| | | | | | | Using a full InputOutput window causes us to make a full Wayland surface for it, and go through the X server. As the goal of the guard window is a window for us to stack minimized windows under so we can prevent them from getting input, it makes sense to use an InputOnly window here.
* window-actor: Fix unobscured_region handling when computing paint volumeAdel Gadllah2014-01-311-1/+1
| | | | | | | | | | | | We currently ignore the unobscured region when we have mapped clones in meta_window_actor_process_damage and meta_window_actor_damage_all but use it unconditionally when computing the paint volume. This is wrong. We should ignore it there as well or we will end up with empty clones if the cloned window is completly obscured (like the tray icons in gnome-shell). https://bugzilla.gnome.org/show_bug.cgi?id=721596
* window: Add "skip-taskbar" propertyFlorian Müllner2014-01-311-0/+17
| | | | | | | | We currently only have a method to query the skip-taskbar hint. Add a corresponding property to allow listening for change notifications. https://bugzilla.gnome.org/show_bug.cgi?id=723307
* window: Remove duplicated function declarationFlorian Müllner2014-01-301-1/+0
|
* main: Make sure to free any events that we get from ClutterJasper St. Pierre2014-01-291-1/+5
|
View Lorry Controller Status