1. 11 Jul, 2022 2 commits
  2. 11 Mar, 2021 4 commits
  3. 16 Dec, 2020 1 commit
  4. 29 Sep, 2020 1 commit
  5. 21 Aug, 2020 1 commit
  6. 26 Jul, 2020 1 commit
    • Emmanuele Bassi's avatar
      Remove ATK · c63087a5
      Emmanuele Bassi authored
      To build a better world sometimes means having to tear the old one down.
              -- Alexander Pierce, "Captain America: The Winter Soldier"
      
      ATK served us well for nearly 20 years, but the world has changed, and
      GTK has changed with it. Now ATK is mostly a hindrance towards improving
      the accessibility stack:
      
       - it maps to a very specific implementation, AT-SPI, which is Linux and
         Unix specific
       - it requires implementing the same functionality in three different
         layers of the stack: AT-SPI, ATK, and GTK
       - only GTK uses it; every other Linux and Unix toolkit and application
         talks to AT-SPI directly, including assistive technologies
      
      Sadly, we cannot incrementally port GTK to a new accessibility stack;
      since ATK insulates us entirely from the underlying implementation, we
      cannot replace it piecemeal. Instead, we're going to remove everything
      and then incrementally build on a clean slate:
      
       - add an "accessible" interface, implemented by GTK objects directly,
         which describe the accessible role and state changes for every UI
         element
       - add an "assistive technology context" to proxy a native accessibility
         API, and assign it to every widget
       - implement the AT context depending on the platform
      
      For more information, see: #2833
      c63087a5
  7. 24 Jul, 2020 1 commit
  8. 11 May, 2020 1 commit
  9. 05 May, 2020 1 commit
  10. 18 Apr, 2020 1 commit
  11. 09 Apr, 2020 1 commit
    • Matthias Clasen's avatar
      Reinstate expected focus behavior · 632524f6
      Matthias Clasen authored
      After the :can-focus change in the previous commit, widgets
      need to set suitable focus and grab_focus implementations
      to implement the desired focus behavior.
      
      This commit does that for all widgets.
      632524f6
  12. 28 Mar, 2020 1 commit
  13. 26 Feb, 2020 1 commit
  14. 25 Feb, 2020 1 commit
  15. 09 Oct, 2019 1 commit
  16. 28 May, 2019 1 commit
  17. 27 May, 2019 1 commit
  18. 05 Feb, 2019 1 commit
  19. 13 Nov, 2018 2 commits
  20. 04 Jun, 2018 1 commit
  21. 05 Apr, 2018 1 commit
  22. 20 Mar, 2018 1 commit
    • Alexander Larsson's avatar
      GtkWidget: Start renaming widget->window · 63e060a2
      Alexander Larsson authored
      This is an automated change doing these command:
      
      git sed -f g gtk_widget_set_has_window gtk_widget_set_has_surface
      git sed -f g gtk_widget_get_has_window gtk_widget_get_has_surface
      git sed -f g gtk_widget_set_parent_window gtk_widget_set_parent_surface
      git sed -f g gtk_widget_get_parent_window gtk_widget_get_parent_surface
      git sed -f g gtk_widget_set_window gtk_widget_set_surface
      git sed -f g gtk_widget_get_window gtk_widget_get_surface
      git sed -f g gtk_widget_register_window gtk_widget_register_surface
      git sed -f g gtk_widget_unregister_window gtk_widget_unregister_surface
      
      git checkout NEWS*
      63e060a2
  23. 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.
      4c150d8e
  24. 18 Nov, 2017 1 commit
  25. 09 Aug, 2017 1 commit
    • Timm Bäder's avatar
      widget: Remove gtk_widget_set_redraw_on_alloc · a8a755e5
      Timm Bäder authored
      Since gtk+ draws more than the widget and allocates more size to it than
      it knows about, this flag doesn't work anymore. Removing it (or setting
      it to TRUE for widgets that used to set it to FALSE) fixes drawing
      invalidation when these widgets get allocated a new size.
      a8a755e5
  26. 20 Jul, 2017 1 commit
  27. 16 Oct, 2016 1 commit
  28. 04 Feb, 2016 1 commit
  29. 20 Dec, 2015 1 commit
  30. 29 Oct, 2015 1 commit
  31. 11 Nov, 2014 1 commit
  32. 14 Aug, 2014 1 commit
    • Phillip Wood's avatar
      Statusbar: Remove matching messages before popping · e853007c
      Phillip Wood authored
      gtk_statusbar_remove_all() was popping the top message if its
      context_id matched before removing other matching messages from the
      stack. This meant that if the context_id of the second top message
      matched it was still displayed when the top message was popped and
      then removed from the list of messages without updating the display.
      Fix this by removing all the matching messages below the top one
      before popping it if it matches.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=724281
      e853007c
  33. 03 Jul, 2014 1 commit
    • Jasper St. Pierre's avatar
      gtkwindow: Remove resize grips · ece9ae4b
      Jasper St. Pierre authored
      Resize grips were introduced for GNOME 3.0, before we had any of the
      "new GNOME app" features like invisible borders and CSD. With OS X 10.6
      and 10.7, Apple has replaced the classic grips in their applications
      with invisible borders as well.
      
      New GNOME app designs don't use resize grips anymore and the new
      default theme for GTK+, Adwaita, disables them entirely by forcing their
      width and height to 0.
      
      They're past their time. Remove the code to support them. This can
      always be reverted if some app relies on them.
      ece9ae4b
  34. 28 May, 2014 1 commit
  35. 07 Feb, 2014 1 commit