|
More flexibility for extra slection choices
|
|
10-09-2013, 13:22
Post: #2
|
|||
|
|||
|
RE: More flexibility for extra slection choices
I understand the reasons for your request.
Let's start with the easy part. I don't think there are any problems with allowing the different extras to be selected individually. As you suggested, this could be done by setting the default value of showExtras to albumDisc, completeAlbum, showAll, tagView and allowing people to customize which combination of these they want to see. It would also make sense to allow the displayed text to be renamed, for example: completeAlbum:Komplettes Album, showAll:Alle Anzeigen Now for the more difficult part. I'm still not convinced that it would make sense to allow the "Hide Contents" step to be removed. This extra step is somewhat inconvenient, but it prevents unpleasant surprises with having duplicate tracks or extra tracks added to the playlist. I understand that some control points have solved this problem either by using UPnP search or by flitering duplicates, but there are many control points that use a naive implementation and I think it's important to make MinimServer work well with these control points. I also understand the argument that an option like this would be used only by expert users who will know how to avoid any problems that this will cause. In practice, I think it's likely that many nonexpert users who find the extra Hide Contents step inconvenient would select the option to remove this step without fully appreciating the consequences of doing this. I would very much like to find a way to overcome the inconvenience of the current approach without the disadvantages mentioned above. One possibility would be to have a way to tell the control point that the container that is protected by the "Hide Contents" choice should be displayed for interactive browsing purposes but should not be used for recursive browsing. For example, this could be done with nonstandard marker elements within the <container> tags for both the "Hide Contents" container and the protected container, and a control point that understands these markers could avoid showing the extra "Hide Contents" menu to the user. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



