1. 25 Oct, 2014 1 commit
  2. 20 Oct, 2014 1 commit
  3. 16 Oct, 2014 1 commit
  4. 15 Aug, 2014 1 commit
  5. 14 Aug, 2014 2 commits
    • Debarshi Ray's avatar
      GtkSpinButton: Prevent public API from unsetting the adjustment · 137abd6f
      Debarshi Ray authored
      A spin button really needs an adjustment to work. So don't let the
      user unset the adjustment by passing NULL to
      gtk_spin_button_set_adjustment.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=734660
      137abd6f
    • Debarshi Ray's avatar
      GtkSpinButton: Always emit value-changed when the adjustment is changed · 1e304e6d
      Debarshi Ray authored
      Changing adjustment via the property setter would not emit
      value-changed, however changing it via gtk_spin_button_configure would.
      
      This inconsistency had the following side-effects:
      
        - Setting an adjustment with a different value would not update the
          value shown by the spin button.
      
        - Creating a spin button like this (common in GtkBuilder XML) will
          not show the initial value:
            g_object_new (GTK_TYPE_SPIN_BUTTON, "adjustment", adj, NULL);
      
      Let's use the same code path (ie. gtk_spin_button_configure) for all
      public facing API for setting adjustment. The code that handled the
      details of swapping out the old adjustment with the new has been split
      into an unset_adjustment method and the rest has been folded into
      gtk_spin_button_configure.
      
      A spin button really needs an adjustment to work, so we don't need
      most of the NULL checks. However we do need to check in
      unset_adjustment because setting a new adjustment during object
      creation might try to unset a non-existent one.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=734660
      1e304e6d
  6. 12 Aug, 2014 1 commit
  7. 19 Jul, 2014 2 commits
  8. 18 Jul, 2014 1 commit
  9. 09 Jun, 2014 1 commit
  10. 27 May, 2014 1 commit
  11. 23 May, 2014 6 commits
  12. 09 May, 2014 2 commits
  13. 19 Feb, 2014 1 commit
  14. 15 Feb, 2014 1 commit
  15. 07 Feb, 2014 1 commit
  16. 04 Feb, 2014 1 commit
  17. 29 Jan, 2014 2 commits
  18. 23 Oct, 2013 1 commit
  19. 20 Jul, 2013 2 commits
    • Matthias Clasen's avatar
      Drop some unnecessary includes · 2f1fa7cd
      Matthias Clasen authored
      Drop includes of deprecated headers where they are
      no longer needed.
      2f1fa7cd
    • Matthias Clasen's avatar
      Move wholly deprecated classes to gtk/deprecated/ · 0aa57d26
      Matthias Clasen authored
      We've recently a number of classes wholly. For these cases,
      move the headers and sources to gtk/deprecated/ and adjust
      Makefiles and includes accordingly.
      
      Affected classes:
      GtkAction
      GtkActionGroup
      GtkActivatable
      GtkIconFactory
      GtkImageMenuItem
      GtkRadioAction
      GtkRecentAction
      GtkStock
      GtkToggleAction
      GtkUIManager
      0aa57d26
  20. 11 Jul, 2013 1 commit
  21. 09 Jul, 2013 1 commit
  22. 03 Jul, 2013 1 commit
  23. 23 Apr, 2013 2 commits
  24. 08 Mar, 2013 2 commits
  25. 04 Mar, 2013 1 commit
  26. 07 Feb, 2013 1 commit
    • Alexander Larsson's avatar
      Add gtk_widget_(un)register_window · 3d4cd4db
      Alexander Larsson authored
      This replaces the previously hardcoded calls to gdk_window_set_user_data,
      and also lets us track which windows are a part of a widget. Old code
      should continue working as is, but new features that require the
      windows may not work perfectly.
      
      We need this for the transparent widget support to work, as we need
      to specially mark the windows of child widgets.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=687842
      3d4cd4db
  27. 19 Sep, 2012 1 commit
    • Cosimo Cecchi's avatar
      spinbutton: fix style context path for internal buttons · 2d5fa785
      Cosimo Cecchi authored
      We were adding one child too much to the style context path when
      generating it for the internal buttons, which in turn caused sibling
      selectors from the theme such as :first-child to apply to both buttons
      under certain circumstances. Spotted by Lapo Calamandrei.
      2d5fa785
  28. 03 Sep, 2012 1 commit