1. 18 Nov, 2010 3 commits
  2. 28 Oct, 2010 1 commit
  3. 23 Oct, 2010 1 commit
    • Owen W. Taylor's avatar
      introspection: remove --allow-unprefixed · 52bc675f
      Owen W. Taylor authored
      Remove --allow-unprefixed option to the scanner, and fix resulting
       * theme.h and boxes.h are split into a main -header and a private
         header that includes stuff that is not generally useful and
         hard to introspect. Merge theme-parser.h into theme.h.
       * meta_display_get_atom() and meta_window_get_window_type_atom()
         are marked as (skip)
       * Fix annotation: (element-type Strut) => (element-type Meta.Strut)
  4. 24 Sep, 2010 2 commits
  5. 23 Sep, 2010 2 commits
    • Florian Müllner's avatar
      Allow breaking out from tiling during a mouse resize · 635e20d0
      Florian Müllner authored
      Extend the code which allows resizing maximized windows using
      alt-middle-drag, so that it applies to tiled windows as well.
    • Owen W. Taylor's avatar
      Allow breaking out from maximization during a mouse resize · 1c3f7c40
      Owen W. Taylor authored and Florian Müllner's avatar Florian Müllner committed
      A maximized window can't be resized from the screen edges (preserves
      Fitts law goodness for the application), but it's still possible
      to start a resize drag with alt-middle-button. Currently we just
      don't let the user resize the window, while showing drag feedback;
      it's more useful to let the user "break" out from the resize.
      This provides a fast way to get a window partially aligned with
      the screen edges - maximize, then alt-drag it out from one edge.
      Behavior choices in this patch:
       - You can drag out a window out of maximization in both directions -
         smaller and larger. This can be potentilaly useful in multihead.
       - Dragging a window in only one direction unmaximizes the window
         fully, rather than leaving it in a horizontally/vertically
         maximized state. This is done because the horizontally/vertically
         maximzed states don't have clear visual representation and can
         be confusing to the user.
       - If you drag back to the maximized state after breaking out,
         maximization is restored, but you can't maximize a window by
         dragging to the full size if it didn't start out that way.
      A new internal function meta_window_unmaximize_with_gravity() is
      added for implementing this; it's a hybrid of
      meta_window_unmaximize() and meta_window_resize_with_gravity().
      Port of the metacity patch from Owen Taylor in bug 622517.
  6. 20 Sep, 2010 1 commit
  7. 17 Sep, 2010 1 commit
    • Florian Müllner's avatar
      Implement side-by-side tiling · 97e2b466
      Florian Müllner authored
      When dragging a window over a screen edge and dropping it there,
      maximize it vertically and scale it horizontally to cover the
      corresponding half of the current monitor.
      Whenever a "hot area" which triggers this behavior is entered, an
      indication of window's target size is displayed after a short delay
      to avoid distraction when moving a window between monitors.
  8. 11 Sep, 2010 1 commit
  9. 07 Sep, 2010 1 commit
    • Colin Walters's avatar
      introspection: Build with --warn-fatal, drop fix-meta-rectangle.py hack · 4c076379
      Colin Walters authored
      Cleanly build with --warn-fatal.  Implementation:
      * Liberally apply (skip) where the API is clearly C only, e.g. uses
        XLib.  The theming code and MutterPlugin are skipped too.
      * Add missing (transfer) and (element-type) annotations
      For a few functions that had a comment, I turned it into gtk-doc, but
      I didn't (with a few exceptions) try to write new documentation in
      this pass.
  10. 09 Aug, 2010 1 commit
  11. 14 Jun, 2010 1 commit
    • Owen W. Taylor's avatar
      Fix problem with window unmaximization · ff5a73de
      Owen W. Taylor authored
      A mismerge of the Metacity commit "4943d79d Prevent window self-maximisation"
      caused the window's user set size and position to be saved *before*
      actually resizing the window to the unmaximized position rather than after.
      This meant that after unmaximization the window was in an inconsistent
      state and anything that caused a resize to be queued (like a change in
      window properties by the application) would cause it to pop back to
      the maximized size and position.
  12. 07 Jun, 2010 1 commit
  13. 14 May, 2010 1 commit
    • Tomas Frydrych's avatar
      _MUTTER_HINTS · 28767c4d
      Tomas Frydrych authored
      A per-window _MUTTER_HINTS property allowing plugins to use custom hints. The
      property holds a colon separated list of key=value pairs; plugin-specific keys
      must be suitably namespaced, while 'mutter-' prefix is reserved for internal
      Mutter use only.
      This commit adds MetaWindow::mutter-hints property, and
      meta_window_get_mutter_hints() accessor, as well as the internal machinery for
      reading and updating of the hints.
  14. 05 May, 2010 1 commit
  15. 26 Apr, 2010 1 commit
  16. 17 Mar, 2010 1 commit
  17. 15 Feb, 2010 1 commit
  18. 11 Feb, 2010 2 commits
  19. 10 Feb, 2010 3 commits
  20. 22 Jan, 2010 1 commit
    • Owen Taylor's avatar
      Cleanup: split MetaSide from MetaDirection · 0aace523
      Owen Taylor authored
      The MetaDirection enumeration had META_SIDE_* values in it that
      were used in some places where an enum with only four directions
      was needed. Split this off into a separate enum called MetaSide
      and use that enum name where appropriate.
  21. 20 Jan, 2010 1 commit
  22. 20 Nov, 2009 2 commits
  23. 17 Nov, 2009 2 commits
  24. 12 Nov, 2009 1 commit
    • Owen W. Taylor's avatar
      Correctly initialize window->input field · fb45b8f4
      Owen W. Taylor authored
      With the change from bug 582639, we no longer call the reload
      functions for properties that are not initially set, so the
      initialization of fields in window.c has to match what
      window-props.c would set for a missing property.
      There was only one discrepancy, window->input, which needs
      to be set to TRUE by default (or a window missing a WM_HINTS
      property won't get focus); we also add explicit initializers
      for a couple of fields that were getting 0-initialized
      to the correct default value of FALSE for consistency with
      the explicit intialization of the rest of the fields.
      Bug reported by Dominique Leuenberger
  25. 22 Oct, 2009 1 commit
  26. 14 Oct, 2009 1 commit
  27. 07 Oct, 2009 2 commits
  28. 02 Oct, 2009 1 commit
    • Owen W. Taylor's avatar
      Use "later functions" to fix priority problems with Clutter redraw · 3508c4aa
      Owen W. Taylor authored
      There was a problem where if, for example, a restack was triggered
      out of a clutter event handler, then after Clutter processed the
      events, it would proceed immmediately on to repaint the stage without
      ever returning control to the GLib main loop. So even though we
      had an idle handler installed with a higher priority than the
      Clutter stage repainting the clutter stage repainting would happen
      first and we'd get a wrong frame.
      Fix this by introducing the idea of "later functions", which abstract
      the idea of "doing something later" away from g_idle_add() and use
      a combination of GLib idle functions and Clutter "repaint functions"
      to get our callbacks triggered at the right time, even when they
      are installed from a clutter event handler.
      This also resolve a FIXME where MUTTER_PRIORITY_BEFORE_REDRAW
      could starve stage repainting.
  29. 22 Sep, 2009 1 commit
  30. 04 Sep, 2009 1 commit