1. 02 Jul, 2015 2 commits
  2. 01 Jul, 2015 3 commits
  3. 11 Jun, 2015 1 commit
  4. 08 Jun, 2015 1 commit
  5. 02 Jun, 2015 1 commit
  6. 30 Apr, 2015 1 commit
  7. 28 Apr, 2015 1 commit
  8. 27 Apr, 2015 1 commit
    • Matthias Clasen's avatar
      GtkWidget: Use the new helpers · b53b38ff
      Matthias Clasen authored
      Instead of issuing g_warning, fill the provided GError.
      This lets us test this error handling, and is the right
      thing to do. Use the new GtkBuilder helpers and
      g_markup_collect_attributes to do so.
  9. 26 Apr, 2015 1 commit
  10. 24 Mar, 2015 1 commit
    • Benjamin Otte's avatar
      cssnode: Clear widget path more aggressively · fdc620cd
      Benjamin Otte authored
      When recomputing CSS, we need a correct widget path in the fallback mode
      where we're still using widget paths.
      So we need to invalidate it everytime it actually changes, and not just
      when emitting the style-updated signal.
      Fixes css-match-regions reftest.
  11. 22 Mar, 2015 1 commit
  12. 18 Mar, 2015 10 commits
  13. 16 Mar, 2015 3 commits
  14. 08 Mar, 2015 1 commit
  15. 07 Mar, 2015 1 commit
  16. 05 Mar, 2015 1 commit
  17. 03 Mar, 2015 1 commit
    • Matthias Clasen's avatar
      Fix 7c4bf742 · 3569d373
      Matthias Clasen authored
      The objects-finalize test constructs gestures with NULL as
      a widget. The recent addition of weak references was not
      ready for that.
  18. 02 Mar, 2015 2 commits
    • Carlos Garnacho's avatar
      gtkwindow: Move window dragging to a standalone drag gesture · 13e22e20
      Carlos Garnacho authored
      The gesture is hooked to the capture phase, so it works for buttons in
      header bars and whatnot. In order to be friendly to the widget it is
      capturing events from, an ugly hack is in place to avoid capturing
      events when the target widget has a gesture that would consume motion
    • Debarshi Ray's avatar
      eventcontroller, widget: Don't crash if destroyed before the other · 7c4bf742
      Debarshi Ray authored
      There are two scenarios. A widget sub-class owns a GtkEventController
      and passes itself to it, or a controller owned by something else is
      passed a widget.
      In the second case, if the widget is destroyed before the controller,
      we will have a crash when destructing the controller because we will
      be accessing invalid memory. Adding a weak reference on the widget
      addresses that problem.
      This leads to a crash in the first case. When the widget is getting
      destroyed, it will drop the reference to its own controller. The
      controller will skip touching the widget because the weak reference
      would have turned it to NULL. However, when the widget sub-class chains
      up to GtkWidget it will try to free all the controllers in its list.
      Unfortunately, all these controllers have already been destroyed. So
      we need to guard against this too.
  19. 19 Feb, 2015 2 commits
  20. 05 Feb, 2015 1 commit
    • Benjamin Otte's avatar
      css: Add -gtk-dpi CSS property hack · 89f635fe
      Benjamin Otte authored
      This property is necessary to ensure widgets automatically update after
      the text scale factor is changed desktop-wide.
      And if I'm already doing a property like this, I can make it
      overridable. So now you can override the dpi per-widget with CSS like
      GtkSwitch {
        -gtk-dpi: 48;
      if you want to debug things.
      Long-term, we want to get rid of this property and insist on dpi being
      96 everywhere and people can change the font size to get larger fonts.
  21. 28 Jan, 2015 2 commits
  22. 27 Jan, 2015 1 commit
  23. 22 Jan, 2015 1 commit