|
|
I don't understand your proposal. It is ok for Column settings dialog box that you get from the context menu of List / List (by Album) view header. But, that dialog is dependent on the current node and current view. How it could be used in the Options dialog that has global options? This is the same problem that I mentioned about Manage views dialog in 0022428. |
|
|
This issue is about the Column settings controls in the Options dialog box. Column settings in Options dialog.png (34,825 bytes) |
|
|
I misunderstood your original feedback. We could make the following tweaks to make it more clear: Column settings --> Field/Column scope Define column settings --> Apply field/column settings in a View to: Each Node in each Collection --> Individual nodes in each Collection Each Collection --> Individual Collections |
|
|
Ok, but what about issue 0022516? What "The entire Library" means? Does it include Folders node, or Playlists node, or any other nodes that don't belong to any Collection? |
|
|
'The Entire Library' refers to the library (i.e. it doesn't include Playing or Folders). |
|
|
What is the reason that the Column settings are limited only to the Library and collections, but not for Folders and Playing? I am sure there are many users who would want to have the same Column settings for all file lists, including nodes outside of collections, like those in Folders, Playing or Playlists nodes. I think they should not be treated any different than e.g. Entire Library > Location nodes. |
|
|
The UI below addresses the concern raised at 0022411:0083490. The following strings better explain the current implementation without revamping the design. --Column, field, and sort configuration scope----------- Share Column, field, and sort settings for each View across: ( ) the entire application ( ) the entire Library ( ) each Collection ( ) each node type in each Collection As to the tooltips: -the entire application: Shares compatible views across collections, Folders, playlists, search results and the main Playing view. Playing and playlists retain their saved play order. The compact Playing panel stays separate. Existing narrower settings are restored when you return to their scope. --> Shares these View settings across all Collections, plus Folders, Playlists, Playing, and Search results (though sort order is ignored for Playing and playlists, and the Playing panel's settings are separate). Question: what does it mean when you indicate 'Existing narrower settings are restored when you return to their scope.'? the entire Library Share settings across all collections. Folders, Playing and other special areas keep their separate settings. --> Shares these View settings across all Collections. Folders, Playing and other special nodes have separate settings. each Collection Applies to columns, fields below artwork, Summary and sorting in compatible built-in views. Elements have a separate scope. Custom views share their settings wherever they are used. --> Shares View settings (columns, fields next to artwork, sorting) across all nodes per Collection. Exception: Each Custom view has separate settings that apply globally. each node type in each Collection Applies to columns, fields below artwork, Summary and sorting in compatible built-in views. Elements have a separate scope. Custom views share their settings wherever they are used. --> Only shares View settings (columns, fields next to artwork, sorting) across similar nodes per Collection. Exception: Each Custom view has separate settings that apply globally. |
|
|
This is a way much better description. And it is great that you will add "the entire application" as an option. However, I am not sure about the term "the entire Library". First of all, the users who do not read description could think that that option applies only to the "Entire Library" node since they have very similar wording. Secondly, does that option include Playlists node? The playlists from that node are stored in the database, which is the same thing as the Library, right? If that option does not include Playlists node, I would call that option just "All Collections". |
- Anonymous
