Version: 2.0 2.fc10 (using KDE 4.1.3) Installed from: Fedora RPMs Searching the collection does not always expand to show items that match the search. To Reproduce: 1) With the collection collapsed so that only Local Collection is visibile. 2) Enter part of the name of a song that you have 3) Nothing happens. Expected the collection to expand to show the items that match the current query, but instead it only will display stuff that was already expanded, if nothing was expanded then the collection will just display "Local Collection".
I think you misunderstand how the system works. The filter is subtractive, not additive. What you do is expand the collection, then enter the filter terms, and then Amarok will remove any non matching items.
Actually I do know how it works. When you enter filter terms the collection is filtered such that only things that match the terms are visible in the collection. The issue is that the tree itself remains collapsed. Previously the tree would be expanded when the filter was used. Example: Enter NOFX in the filter. The collection would show NOFX and all the songs under the artist. Or Enter Fish The first couple matching entries in the collection would be expanded down to the track level, after that the ones below would be expanded to perhaps artist. The thing missing is that the collection would uncollapse as the filter was used. It was and extremely handy thing. Sounds like that instead of a bug, this is an enhancement.
Fiddled with the behaviour of 1.4 Amarok. The tree is expanded as the filter narrows the total collection of things. In my collection entering fish expands the tree to display a couple songs, clearing the filter causes the collection to contract. Clearly this behaviour was intended at 1.4 and was not included into 2.0. It is incredibly handy and makes the filter much more useful. As it is now with 2.0, I enter a search term, expand the tree, expand one of the artists, expand one of the albums, and finally see the song. This is OK if I know the exact term I am looking for, but, if I am using the filter to only narrow my choices it is far more difficult and requires that I expand each potential selection by hand to find what I am looking for.
It's not a bug, but a missing feature. Added to the whislist as high priority.
*** This bug has been marked as a duplicate of bug 172379 ***