1. 25 Jun, 2018 1 commit
  2. 20 Jun, 2018 1 commit
  3. 26 Apr, 2018 1 commit
  4. 11 Apr, 2018 4 commits
  5. 10 Apr, 2018 1 commit
  6. 05 Apr, 2018 1 commit
  7. 28 Mar, 2018 1 commit
  8. 20 Mar, 2018 2 commits
  9. 17 Mar, 2018 4 commits
  10. 04 Mar, 2018 1 commit
  11. 08 Feb, 2018 1 commit
  12. 06 Feb, 2018 1 commit
    • Matthias Clasen's avatar
      The big versioning cleanup · 4c150d8e
      Matthias Clasen authored
      Remove all the old 2.x and 3.x version annotations.
      GTK+ 4 is a new start, and from the perspective of a
      GTK+ 4 developer all these APIs have been around since
      the beginning.
  13. 17 Jan, 2018 1 commit
  14. 03 Jan, 2018 1 commit
    • Timm Bäder's avatar
      Move geometry management docs do GtkWidget · cba24360
      Timm Bäder authored
      Both GtkWidget and GtkContainer had similar docs regarding hfw/wfh
      geometry management. Move these just to GtkWidget. Also make sure the
      examples compile, port everything from gtk_preferred_* to measure and
      replace some occurrences of "container" with "widget" where container
      was just used to refer to a widget with child widgets.
  15. 06 Oct, 2017 1 commit
    • Benjamin Otte's avatar
      build: Enable -Wswitch-enum and -Wswitch-default · 43c212ac
      Benjamin Otte authored
      This patch makes that work using 1 of 2 options:
      1. Add all missing enums to the switch statement
      2. Cast the switch argument to a uint to avoid having to do that (mostly
         for GdkEventType).
      I even found a bug while doing that: clearing a GtkImage with a surface
      did not notify thae surface property.
      The reason for enabling this flag even though it is tedious at times is
      that it is very useful when adding values to an enum, because it makes
      GTK immediately warn about all the switch statements where this enum is
      And I expect changes to enums to be frequent during the GTK4 development
  16. 03 Sep, 2017 1 commit
  17. 21 Aug, 2017 2 commits
  18. 07 Aug, 2017 2 commits
    • Daniel Boles's avatar
      Container: Don’t scroll to unset focus child coord · 23b6699e
      Daniel Boles authored
      In gtk_container_real_set_focus_child(), we try to scroll to the
      position of the new :focus-child if we have h or v adjustments.
      gtk_widget_translate_coordinates() returns FALSE if neither widget is
      realized or in other situations that cause output parameters x and y not
      to be set. Thus, if the caller did not initialise x/y and uses them even
      if the function returned FALSE, they are using uninitialised variables.
      In gtk_container_real_set_focus_child(), we did not check the return
      value but merrily went ahead and used x and y regardless. This is UB, as
      revealed by Valgrind, as well as being pointless.
      The trivial fix is to exit early if (!gtk_widget_translate_coordinates).
    • Daniel Boles's avatar
      Container: Fix scrolled coord in set_focus_child() · c4865bed
      Daniel Boles authored
      Commit 885bcd9f trampled the bit here
      that is meant to translate between the nominated focus child and the
      actual innermost one that is used for updating the h/v adjustments.
      So, we need to save the passed focus child before diving into its
      children, then translate and get allocations between them both. This
      makes GTK+ 4 behave like GTK+ 3 again: instead of priv->focus_child and
      focus_child, we now have focus_child and child, serving the roles of the
      nominated focus child and its innermost focus child respectively.
      This also ditches the unnecessary call to Widget:get_focus_child(), as
      Container::set_focus_child() gets that same new child as an argument.
  19. 20 Jul, 2017 6 commits
  20. 25 Apr, 2017 2 commits
  21. 31 Mar, 2017 3 commits
  22. 07 Jan, 2017 2 commits