1. 27 Jun, 2014 5 commits
  2. 26 Jun, 2014 9 commits
  3. 25 Jun, 2014 1 commit
  4. 24 Jun, 2014 5 commits
  5. 21 Jun, 2014 3 commits
  6. 19 Jun, 2014 1 commit
  7. 17 Jun, 2014 5 commits
    • Jasper St. Pierre's avatar
      compositor: Simplify meta_window_actor_set_updates_frozen · 24d7c5eb
      Jasper St. Pierre authored
      Since we always call it with the same value, just push that
      value into the implementation.
    • Jasper St. Pierre's avatar
      window: Move placement code from the constraints path · dc6decef
      Jasper St. Pierre authored
      This way, it's implemented as a special case in move_resize_internal,
      which makes it a lot easier to manage.
    • Jasper St. Pierre's avatar
      constraints: Clean up logical operations · 25d7e480
      Jasper St. Pierre authored
      The logical version of the bitwise XOR operator ^ is !=. I don't
      know why XOR was even used in the first place.
    • Jasper St. Pierre's avatar
      window: Save the buffer_rect internally · b0b8f372
      Jasper St. Pierre authored
      Rather than calculate it speculatively with the current properties
      which may be too new or too out of date, make sure it always fits
      with the proper definition. We update it when we update the toplevel
      window for X11, and when a Wayland surface is committed with a newly
      attached buffer.
    • Jasper St. Pierre's avatar
      window: Rename get_input_rect to get_buffer_rect · 188e4e1b
      Jasper St. Pierre authored
      With get_input_region existing, get_input_rect is a misnomer. Really,
      it's about the geometry of the output surface, and it's only used that
      way in the compositor code.
      Way back when in GNOME 3.2, get_input_rect was added when we added
      invisible borders. get_outer_rect was always synonymous with server-side
      geometry of the toplevel. get_outer_rect was used for both user-side
      policy (the "frame rect") and to get the geometry of the window.
      Invisible borders were meant to extend the input region of the frame
      window silently. Since most users of get_outer_rect cared about the
      frame rect, we kept that the same and added a new method, get_input_rect
      to get the full rect of the framed window with all invisible borders for
      input kept on.
      As time went on and CSD and Wayland became a reality, the relationship
      between the server-side geometry and the "frame rect" became more
      complicated, as can be evidenced by the recent commits. Since clients
      don't tend to be framed anymore, they set their own input region.
      get_buffer_rect is also sort of a poor name, since X11 doesn't really
      have buffers, but we don't really have many other alternatives.
      This doesn't change any of the code, nor the meaning. It will always
      refer to the rectangle where the toplevel should be placed.
  8. 16 Jun, 2014 2 commits
    • Jasper St. Pierre's avatar
      window: Fix get_input_rect in a hacky way · 9d5273bb
      Jasper St. Pierre authored
      All of the users of get_input_rect don't actually want a synthesized
      input rect based off of the current margins. What they really want is
      the last-configured size of the toplevel window.
      Since we don't properly track this anymore in the generic MetaWindow,
      use XGetWindowAttributes to fetch a server-side rectangle. This is a
      bad layer violation, but since the window geometry code will have to
      be rewritten anyway for the Wayland set_window_geometry, let's just
      push a hacky fix for now.
    • Jasper St. Pierre's avatar
  9. 14 Jun, 2014 5 commits
  10. 12 Jun, 2014 4 commits