1. 10 Dec, 2017 1 commit
  2. 25 Jul, 2017 1 commit
    • Carlos Garnacho's avatar
      gtklinkbutton: Set cursor on button's event window · 0daf7967
      Carlos Garnacho authored
      Setting the cursor on the widget window (i.e. the parent widget's) is
      finicky because the cursor needs to be updated on crossing events, and
      will yield the wrong result for other master devices that happen to be
      in other areas of the same parent widget's window.
      
      Just set it always on the event window created by the GtkButton parent
      class. That window was causing the crossing events, so the rectangle
      that gets the hand cursor set will be the same size, and we don't need
      to track pointer crossing state that way.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=785375
      0daf7967
  3. 08 May, 2017 1 commit
  4. 16 Feb, 2017 1 commit
  5. 19 Jul, 2016 1 commit
  6. 13 Jul, 2016 1 commit
  7. 28 Apr, 2016 1 commit
  8. 28 Feb, 2016 1 commit
  9. 30 Oct, 2015 1 commit
  10. 23 Sep, 2015 1 commit
  11. 26 Jul, 2015 1 commit
  12. 05 Jul, 2015 1 commit
  13. 09 Jun, 2014 1 commit
  14. 19 Feb, 2014 1 commit
  15. 07 Feb, 2014 1 commit
  16. 04 Nov, 2013 1 commit
  17. 18 Aug, 2013 1 commit
    • Matthias Clasen's avatar
      Add a style class for context menus · 624ec0fb
      Matthias Clasen authored
      Attached widgets inherit from the style of the widget they are
      attached to. This can sometimes have unintended consequences,
      like a context menu in the main view of gedit inheriting the font
      that is configured for documents, or the context menu of the preview
      in the font chooser coming up with humongous font size.
      
      To fix this problem, we introduce a context menu style class
      and use it for all menus that are used like that. The theme
      can then set a font for this style class.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=697127
      624ec0fb
  18. 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
  19. 09 Jul, 2013 1 commit
  20. 25 Jun, 2013 1 commit
  21. 10 May, 2012 1 commit
  22. 13 Apr, 2012 1 commit
  23. 27 Feb, 2012 1 commit
  24. 18 Dec, 2011 1 commit
  25. 02 Nov, 2011 1 commit
  26. 23 Oct, 2011 1 commit
  27. 27 Sep, 2011 1 commit
  28. 26 Sep, 2011 1 commit
  29. 16 Sep, 2011 1 commit
  30. 05 Jul, 2011 1 commit
  31. 10 Jun, 2011 1 commit
  32. 07 Feb, 2011 1 commit
  33. 04 Jan, 2011 2 commits
  34. 21 Dec, 2010 1 commit
  35. 15 Dec, 2010 1 commit
  36. 15 Oct, 2010 1 commit
    • Emmanuele Bassi's avatar
      link-button: Add ::activate-link signal · 17ffcb0c
      Emmanuele Bassi authored
      We cannot use the GtkButton::clicked signal to override the default
      behavior of GtkLinkButton (i.e. call gtk_show_uri()), because
      GtkButton::clicked is registered as a RUN_FIRST signal, which obviously
      prevents any other signal handler connected to it to stop the
      propagation before the class handler has a chance to run.
      
      For this reason we can add a GtkLinkButton::activate-link signal, which
      will be emitted by the default GtkButton::clicked signal handler; the
      ::activate-link signal has a boolean return value, which allows simpler
      code for stopping the propagation to the next signal handler.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=632150
      17ffcb0c
  37. 26 Sep, 2010 1 commit
    • Benjamin Otte's avatar
      Move GtkSizeRequest into GtkWidget · d9c92598
      Benjamin Otte authored
      It doesn't make sense to keep them separate as GtkSizeRequest requires a
      GtkWidget and GtkWidget implements GtkSizeRequest, so you can never have
      one without the other.
      It also makes the code a lot easier because no casts are required when
      calling functions.
      
      Also, the names would translate to gtk_widget_get_width() and people
      agreed that this would be a too generic name, so a "preferred" was added
      to the names.
      
      So this patch moves the functions:
      gtk_size_request_get_request_mode() => gtk_widget_get_request_mode()
      gtk_size_request_get_width() => gtk_widget_get_preferred_width()
      gtk_size_request_get_height() => gtk_widget_get_preferred_height()
      gtk_size_request_get_size() => gtk_widget_get_preferred_size()
      gtk_size_request_get_width_for_height() =>
        gtk_widget_get_preferred_width_for_height()
      gtk_size_request_get_height_for_width() =>
        gtk_widget_get_preferred_height_for_width()
      ... and moves the corresponding vfuncs to the GtkWidgetClass.
      
      The patch also renames the implementations of the vfuncs in widgets to
      include the word "preferrred".
      d9c92598
  38. 24 Sep, 2010 1 commit