View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003898 | MMW v4 | DB/FileMonitor | public | 2007-11-02 21:01 | 2007-11-26 22:30 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003898: Track Browser: Leftmost column is sometimes unnecessarily restricted | ||||
| Description | I'm not sure what triggers this (other than a DB scan), however, the track browser normally works correctly (i.e. the first column is most general, the second column narrows the selection a bit, and the third column narrows it further). Sometimes, however, clicking an entry in the second column causes the first column's selection to narrow to the subset that matches the second column (I've noticed that it happens after a DB scan or after a CD Rip has completed). In case this is confusing, here's an example (three colums are Genre, Artist, Album): AllAllAll g1 A1 Alb1 g2 A2 Alb2 g3 A3 g4 Normally if the user selects G2 --> A1, A2 , A3 is listed Normally if the user selects A2 --> Alb1, Alb2 are listed BUT in the buggy case, when A2 is selected -->Alb1, Alb2 are listed and the list of Genres is shortened to only include G2! Note: The browser could work either like iTunes (where selection is always narrowed from left to right) or it could be directionally independent (I prefer the former). But whichever approach we take, it should be consistent. | ||||
| Additional Information | Reported at: http://www.mediamonkey.com/forum/viewtopic.php?t=22181 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1106 | ||||
|
|
This issue was fixed with issue 3914. Will be in 1099. |
|
|
After playing with the Track browser in 1103, it seems that the current incarnation of the browser is not very useful since it doesn't adjust adjacent columns at all to help the user narrow down choices. Eg, if I choose Artist=U2, then the Album column doesn't change to only show U2 albums. This makes it very easy to select 'non-matching' attributes (that don't have any associated tracks) which in turn triggers a reset to the columns. This end up happening 90% of the time, makeing the Track Browser useless for browsing. We should fix the columns so that they work exactly as iTunes does: -Leftmost column is the first filter -Middle column displays items that match the first, and filters additionally -Third column display items that match the first 2 filters, and filters additionally -Clicking 2nd or 3rd column without clicking one to the left has no effect on columns to the left -Clicking on 'all' in any column causes all Entries in that column to be displayed, along with All entries for columns to the right In addition as today: -Filters limit what appears in the miller columns -Tree nodes limit what appears in the miller columns -Searches limit what appears in the miller columns -Clicking tracks should have no effect Default column values should be from General to more specific e.g. Genre, Artist, Album. |
|
|
I've also notice, that clicking around in any column, when it works, will sometimes also clear and refresh the column you clicked in (even though the data doesn't change). Since the data will in the column you click in will never change from that click, it should never appear to refresh. refreshiung is confusing and makes the browser look less reliable. as Rusty mentioned, it shoudl only refresh the columns to it's right... not to the left and NOT ITSELF. I've found this only sometimes happens, when clicking on items but almost always happens when clicking on "All" Dale. |
|
|
Fixed. Will be in 1104. |
|
|
Tested 1103--MUCH better. The only issue is that there are some cases where the latter 2 miller columns don't refresh a) Click a tree node, then click an entry in the first miller column, then click another tree node --> Latter 2 columns only show 'All'. The user has to click 'All' to trigger relevant entries to appear. b) An issue similar to the above occurs when the Search bar is used (instead of clicking a node). |
|
|
Fixed. Will be in 1105. |
|
|
Verified 1105. There's just 2 more items: 1) Search Entire Library works fine, but Search Selected doesn't restrict the miller columns as it probably should. e.g. If node Genre=Folk is selected, then the miller columns are restricted to values that have tracks with Genre=Folk. If the user then Searches for 'love' then the miller columns should be further restricted, but they aren't (only the tracklist is further constrained). Note: this contradicts my original comment in 0003266, however, upon further reflection I now see what Dale had meant, and realize that he was correct. This also means that the behaviour that Ludek described in 0003854 comment 11672 is actually not a bug--the original behaviour is preferable. 2) The Default column values should be from General to more specific e.g. Genre, Artist, Album (instead of Artist, Album, Genre). |
|
|
Fixed in 1106. |
|
|
Verified 1108. |
