Comment 1 for bug 1412453

Original, the browse view was designed to just see the truth from the HD like a file manager would do.

Since many users, including me know sometimes a track by store position in a file system folder, It is more continent to find it in the broth tree, than sort and filter the library by location.

I am also aware that not only a few user select all of there tracks from th browse tree. IMHO this just works by an accident ;-) .. because the user experience is real bad: No library support, Slow and tree navigation feels bad.

https://bugs.launchpad.net/mixxx/+bug/1179318
https://bugs.launchpad.net/mixxx/+bug/1160525
https://bugs.launchpad.net/mixxx/+bug/925628
https://bugs.launchpad.net/mixxx/+bug/1376709
https://bugs.launchpad.net/mixxx/+bug/909959
https://bugs.launchpad.net/mixxx/+bug/797440
https://bugs.launchpad.net/mixxx/+bug/1196311
https://bugs.launchpad.net/mixxx/+bug/1259064
https://bugs.launchpad.net/mixxx/+bug/1166278

On the other hand we it is a common wish to feature a hierarchical structure of tracks of any type.

So I think before rushing into a quick hack solution, we may consider to implement this bug:
Virtual folders below the Library tree node:
This was discussed here:
https://bugs.launchpad.net/mixxx/+bug/1228789

A static solution showing all library folders, seams to be a weekend project and would solve the most of the bugs above at once.