1. 16 Mar, 2019 1 commit
  2. 12 Mar, 2019 1 commit
  3. 10 Mar, 2019 1 commit
  4. 08 Mar, 2019 1 commit
  5. 05 Mar, 2019 1 commit
  6. 04 Mar, 2019 1 commit
  7. 03 Mar, 2019 3 commits
  8. 02 Mar, 2019 1 commit
  9. 01 Mar, 2019 2 commits
  10. 28 Feb, 2019 1 commit
  11. 27 Feb, 2019 4 commits
  12. 26 Feb, 2019 1 commit
  13. 24 Feb, 2019 2 commits
  14. 22 Feb, 2019 1 commit
  15. 21 Feb, 2019 1 commit
  16. 20 Feb, 2019 1 commit
  17. 19 Feb, 2019 1 commit
  18. 18 Feb, 2019 5 commits
    • Marinus Schraal's avatar
      Release 3.31.91 · 5f5bde21
      Marinus Schraal authored
      5f5bde21
    • Jean Felder's avatar
      emptyview: Add mock {un}select_all methods · 2b9b90e8
      Jean Felder authored
      EmptyView does not inherit from BaseView anymore. Therefore, it does
      not have any default {un}select_all methods anymore.
      This can lead to a crash when selection_mode is enabled from a view or
      a widget and then a search which returns no result is triggered.
      
      Add select_all and unselect_all methods to EmptyView to prevent this
      crash. These functions do nothing as no song, artist or album can be
      selected from an empty view.
      2b9b90e8
    • Marinus Schraal's avatar
      Revert "window: Fix disable selection-mode on search" · 5d7e8242
      Marinus Schraal authored
      This reverts commit 8abbaaa4.
      
      Allow starting a search in selection mode once again.
      5d7e8242
    • Jean Felder's avatar
      player: Do not reset validation if the playlist is unchanged · e24017a5
      Jean Felder authored
      _validation_indexes keeps track of the songs being validated. Every
      time a new playlist is loaded or a new song from the same playlist is
      loaded by clicking on it, this list is reset. In the latter case, it
      works fine in most of the cases because the discovery mechanism (which
      is asynchronous) is fast enough to end before the user can click on an
      other song. Indeed, the list is already empty when it is reset.
      However, on a slow configuration, it is possible to select an other
      song before the end of the discovery mechanism. So, the validation
      list is reset even if a discovery is running. This results in a crash
      as reported by #252.
      
      The solution is to not reset _validation_indexes if the playlist is
      unchanged. Also, introduce a new ValidationStatus (IN_PROGRESS) when a
      song is being validated. This prevents to queue multiple times the
      same song on a slow configuration.
      
      closes: #252
      e24017a5
    • Jean Felder's avatar
      smoothscale: Prevent negative timeouts · 1d642c0f
      Jean Felder authored
      Smoothscale timeout depends on the scale's width and
      padding. Apparently in some configurations (maybe a custom theme or a
      custom scaling), this width can become negative. This results in a
      crash as a timeout cannot be negative.
      
      Add a max bound to ensure to ensure that the width variable cannot be
      smaller than 1.
      
      Closes: #244
      1d642c0f
  19. 17 Feb, 2019 4 commits
    • Marinus Schraal's avatar
      flatpak: Fix Tracker building · fdd0ab9b
      Marinus Schraal authored
      The feature options now require 'disabled' instead of 'no'.
      fdd0ab9b
    • byStarTW's avatar
      Update Chinese (Taiwan) translation · 80802e6b
      byStarTW authored
      80802e6b
    • Jean Felder's avatar
      searchbar: Fix Match fields sensitivity on source changes · bfec39b8
      Jean Felder authored
      When switching back to the local search after a tag removal, the Match
      fields are still greyed out. Indeed, match fields are only updated
      when a change occurs from the DropDown (coming from selection-changed
      signal).
      
      Moving the update logic to source_manager's active property
      notifications fixes the issue.
      bfec39b8
    • Sagar Lakhani's avatar
      searchbar: Fix SourceManager tag removal · 7e6c2b8b
      Sagar Lakhani authored
      source_manager and search_manager do not have the same default
      value. search_manager's default value is the first one, while
      source_manager's default value is the second one.
      BaseManager's operations assume that a manager's default value is
      always the first one. Therefore, it's impossible to remove the "All"
      source tag from the tags.
      
      Fix the issue by introducing a default_value GObject property.
      source_manager's default value is set to 2. This allows to properly
      reset the tag.
      
      Closes: #92
      7e6c2b8b
  20. 16 Feb, 2019 4 commits
  21. 14 Feb, 2019 2 commits
  22. 13 Feb, 2019 1 commit