1. 09 Nov, 2019 1 commit
  2. 11 Aug, 2019 1 commit
  3. 19 Jul, 2019 1 commit
  4. 28 Jun, 2019 1 commit
  5. 18 May, 2019 1 commit
  6. 17 May, 2019 1 commit
  7. 27 Jan, 2019 1 commit
  8. 24 Jan, 2019 1 commit
  9. 26 Sep, 2018 1 commit
  10. 14 Jun, 2018 1 commit
  11. 06 Jun, 2018 1 commit
  12. 06 Apr, 2018 1 commit
  13. 05 Apr, 2018 1 commit
  14. 15 Feb, 2018 1 commit
  15. 25 Nov, 2017 1 commit
  16. 30 Jun, 2017 1 commit
  17. 13 Feb, 2017 1 commit
  18. 22 May, 2015 2 commits
  19. 17 May, 2015 1 commit
  20. 05 May, 2015 1 commit
  21. 20 Apr, 2015 1 commit
  22. 28 Feb, 2015 1 commit
  23. 19 Feb, 2015 2 commits
  24. 04 Jan, 2015 1 commit
  25. 05 May, 2013 1 commit
  26. 27 Dec, 2012 1 commit
  27. 09 Dec, 2012 1 commit
  28. 02 Dec, 2012 1 commit
  29. 24 Nov, 2012 1 commit
  30. 10 Nov, 2012 1 commit
  31. 31 Oct, 2012 1 commit
  32. 14 Oct, 2012 1 commit
  33. 28 Apr, 2012 1 commit
  34. 15 Apr, 2012 2 commits
    • Jannis Pohlmann's avatar
      Move away from using a hard-coded size for window icons (bug #8626). · 16ab778b
      Jannis Pohlmann authored
      The previous commit wasn't actually related to this bug. The problem
      here was that the xfwm4 tab window now allows themes to change the size
      of the displayed window icons but Thunar still hard-coded its own window
      icons to 48px.
      
      From this commit Thunar on uses thunar_file_get_icon_name(current_dir)
      to get an icon name for the current directory and and then calls
      gtk_window_set_icon_name() rather than asking ThunarIconFactory for a
      48px GdkPixbuf that cannot be scaled up nicely. This is ok because we
      only ever set icons for directories and for those ThunarIconFactory
      never returns anything but a GdkPixbuf based on an icon name anyway. It
      never returns a GdkPixbuf loaded from an absolute path or anything.
      16ab778b
    • Jannis Pohlmann's avatar
      096f3b6e
  35. 13 Apr, 2012 1 commit
  36. 28 Mar, 2012 2 commits