|
|
They shouldn't be pinned but rather they should display like all other fields: in the order in which they appear. In build 2662, Artwork and Summary appear as the last two items in the 'Choose columns' dialog, even though they are the first 2 columns displayed! |
|
|
column-order-incorrect.jpg (63,385 bytes) |
|
|
Fixed |
|
|
Although Artwork and Summary can't be moved, users can still move other columns above them. 1 Selected columns should be divided in 2 sections: a Unsortable columns b Sortable columns It should also indicate that the column sort is reflected in the Filelisting. That way it not only stops the ability for users to sort columns that are unsortable, but also communicates this to the user. Right now there is no feedback to user why Artwork/Summary can't be sorted. As an immediate 5.0.4 solution a horizontal divider could be shown between Artwork/Summary and the other columns and fix the D&D capability of any columns above these fixed columns. Note that the same problem exists in Auto-Tag with the Album Summary column: 0018582 |
|
|
Fixed |
|
|
Added todoc_help since afaik, Album Summary (which appears in 'list (by album)' views and in auto-tag) isn't described and the Track Summary field is only mentioned re. the Player, even though it can appear elsewhere. Perhaps both should appear in the tag/field reference? |
|
|
Verified on 2667 that Artwork/Summary columns can't be moved below other columns, not that other columns can be moved above these. However the interface does not indicate this to the user, and doesn't indicate why it fails to move when user attempts to move them or move other columns above them. The interface should indicate this better. Although at the same time I'm wondering why these 2 columns need to be pinned first? |
|
|
This particular issue is probably as good as it's going to get for 5.0.4. What's really needed for 5.x is improved "Group by" functionality that ties together views and groupings, and makes it obvious how Grouping by e.g. album causes certain items to appear within the view. TBD at 0019416 |
|
|
Closing after reviewed in 2681 Issue is resolved and rest will be handled in related bugs. |
|
|
Conflicts with 0018210:0070506 |
- Anonymous
