1. 12 Mar, 2018 1 commit
  2. 03 Jan, 2018 1 commit
  3. 15 Dec, 2017 1 commit
  4. 11 May, 2017 2 commits
  5. 25 Apr, 2017 1 commit
  6. 19 Dec, 2016 1 commit
  7. 20 Sep, 2016 1 commit
  8. 03 Sep, 2016 2 commits
  9. 29 Aug, 2016 1 commit
  10. 21 Jun, 2016 1 commit
  11. 12 May, 2016 1 commit
  12. 22 Apr, 2016 1 commit
  13. 11 Apr, 2016 1 commit
  14. 28 Feb, 2016 1 commit
  15. 08 Feb, 2016 1 commit
    • Timm Bäder's avatar
      Various documentation fixes · c5369356
      Timm Bäder authored
      Always have Since: annotations at the very bottom, use the correct
      ClassName::signal-name/ClassName:property-name syntax, fix a few typos
      in type names, wrong function names, non-existing type names, etc.
      c5369356
  16. 07 Feb, 2016 1 commit
    • Timm Bäder's avatar
      Remove more unnecessary redraws · c360b5fb
      Timm Bäder authored
      The call to gtk_widget_set_state_flags immediately before these already
      queues a redraw/allocate/resize in case they have to be queued.
      c360b5fb
  17. 06 Jan, 2016 2 commits
  18. 15 Dec, 2015 3 commits
  19. 01 Dec, 2015 1 commit
  20. 30 Nov, 2015 1 commit
  21. 14 Nov, 2015 2 commits
  22. 05 Nov, 2015 1 commit
  23. 03 Nov, 2015 2 commits
  24. 14 Sep, 2015 1 commit
    • Alexander Larsson's avatar
      gtk: Stop setting GDK_EXPOSURE_MASK on random widgets · d5f17549
      Alexander Larsson authored
      These days exposure happens only on the native windows (generally the
      toplevel window) and is propagated down recursively. The expose event
      is only useful for backwards compat, and in fact, for double buffered
      widgets we totally ignore the event (and non-double buffering breaks
      on wayland).
      
      So, by not setting the mask we avoid emitting these events and then
      later ignoring them.
      
      We still keep it on eventbox, fixed and layout as these are used
      in weird ways that want backwards compat.
      d5f17549
  25. 12 Sep, 2015 1 commit
  26. 06 Sep, 2015 1 commit
  27. 03 Sep, 2015 1 commit
  28. 26 Aug, 2015 1 commit
    • Benjamin Otte's avatar
      listbox: Mark activatable rows with a .activatable style class · 207e5930
      Benjamin Otte authored
      Do not use .button anymore.
      
      This is for 2 reasons:
      1. The styling is seperate in our themes, so it doesn't make sense to
         share the style class.
      2. Due to the shared styling of .buton, listbox rows inherit all the
         special case styles that exist for buttons - such as linked buttons,
         header buttons, entry buttons, spinbutton buttons, etc. This means
         that the code has to check all these special cases all the time and
         for listbox rows, this is very slow.
      207e5930
  29. 25 Aug, 2015 2 commits
  30. 22 Aug, 2015 1 commit
  31. 16 Aug, 2015 1 commit
  32. 08 Aug, 2015 1 commit
    • Kalev Lember's avatar
      listbox: Avoid using show_all on rows · d6f51ef7
      Kalev Lember authored
      Don't use gtk_widget_show_all() on row widgets because that would
      unconditionally show all of its children. This might be unwanted in case
      the row implementation wants to keep some of its children hidden.
      
      This commit changes it to use show() instead of show_all() and relies on
      the row widget to control the visibility of its children itself as
      appropriate.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=753392
      d6f51ef7