1. 09 Jun, 2016 6 commits
    • Emmanuele Bassi's avatar
      Add GdkDrawingContext · a7ef37da
      Emmanuele Bassi authored
      Instead of giving out Cairo contexts, GdkWindow should provide a
      "drawing context", which can then create Cairo contexts on demand; this
      allows us to future proof the API for when we're going to use a
      different rendering pipeline, like OpenGL.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=766675
      a7ef37da
    • Emmanuele Bassi's avatar
      Simplify the widget rendering entry point · 2c7b2171
      Emmanuele Bassi authored
      Now that GDK has the appropriate API, we can simplify the widget drawing
      code into a single function.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=766675
      2c7b2171
    • Emmanuele Bassi's avatar
      Add frame drawing API to GdkWindow · fc569f1a
      Emmanuele Bassi authored
      Existing code drawing on a GDK window has to handle the direct drawing
      and the buffered drawing by itself, by checking the window type and
      whether or not the window is backed by a native windowing surface. After
      that, the calling code has to create a Cairo context from the window and
      keep an association between the context and the window itself.
      
      This is completely unnecessary: GDK can determine whether or not it
      should use a backing store to draw on a GdkWindow as well as create a
      Cairo context, and keep track of it.
      
      This allows to simplify the calling code, and enforce some of the
      drawing behavior we want to guarantee to users.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=766675
      fc569f1a
    • Tristan Van Berkom's avatar
      scrolledwindow test: Check natural width for max content size · d6187c9a
      Tristan Van Berkom authored
      The maximum content size does not increase the minimum request
      but only ensures that both minimum and natural requests do not
      exceed the maximum setting.
      d6187c9a
    • Tristan Van Berkom's avatar
      scrolledwindow: Resolve whether we use overlay scrollbars early. · 34feba1e
      Tristan Van Berkom authored
      Widgets should support size requests before being realized in general,
      otherwise this can cause flicker/resize at initial display time as
      the toplevel window can make a request before realize/allocate.
      
      This also makes the added testsuite/gtk/scrolledwindow.c test work again,
      this was broken because we only ever calculate whether we are going
      to use overlay scrollbars once the scrolled window is realized (and
      the test case does not realize any window).
      34feba1e
    • Tristan Van Berkom's avatar
      scrolledwindow: Bug 766569 - General size request fixes. · d7e242ee
      Tristan Van Berkom authored
      This patch does a couple of things:
      
        o Removes the obscure 'extra_width' and 'extra_height' variables
          making the request code exceedingly difficult to read
      
        o Fixes the max-content-size properties introduced in bug 742281
          so that they do not grow the minimum request.
      
        o Cleanup of request code in general:
          - min/max content sizes are clamped around the child request as needed
          - scrollbar requests are only added in one place, after child request
            sizes are calculated and without the extra_width/height thing.
      d7e242ee
  2. 08 Jun, 2016 11 commits
  3. 07 Jun, 2016 2 commits
  4. 06 Jun, 2016 16 commits
  5. 05 Jun, 2016 4 commits
  6. 03 Jun, 2016 1 commit