1. 19 Feb, 2014 5 commits
  2. 18 Feb, 2014 20 commits
  3. 17 Feb, 2014 5 commits
  4. 16 Feb, 2014 5 commits
  5. 15 Feb, 2014 4 commits
    • Allison Karlitskaya's avatar
      idle-monitor: avoid XSyncBadAlarm X error · d043d994
      Allison Karlitskaya authored
      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
      d043d994
    • Jasper St. Pierre's avatar
      a0ef7c71
    • Jasper St. Pierre's avatar
      compositor: Delay meta_compositor_add_window until the first show · 4efe4483
      Jasper St. Pierre authored
      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
      4efe4483
    • Jasper St. Pierre's avatar
      Always map the client and frame windows · aec3edb1
      Jasper St. Pierre authored
      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
      aec3edb1
  6. 13 Feb, 2014 1 commit
    • Giovanni Campagna's avatar
      window: don't set _NET_WM_FULLSCREEN_MONITORS to bogus values · 0c5a6ad7
      Giovanni Campagna authored
      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
      0c5a6ad7