View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003014 | MMW v4 | Properties/Auto-Tools | public | 2007-04-20 11:15 | 2009-02-20 00:17 |
| Reporter | jiri | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.1 | ||||
| Summary | 0003014: Improved input mechanism for multiple value fields | ||||
| Description | Currently there are several fields with possibility to have multiple values, like Artist or Genre. These are stored in DB so that multiple values are separated by ';'. However, the same format is used for presentation to user and this might not always be wanted. A possible approach would probably be to let user define in Options dialog which characters to use as mutliple fields separators, e.g. something like: Characters treated as separators: _';', ',', '&'______ Character shown as separator: _ & ________________ (The first line being used as a list of accepted separators, the second for separator that will MM always use when presenting the value to user). As discussed with Petr, the drop-downs in Properties dialog (and for in-place editing) could also be improved so that it's easier for user to enter multiple values. Some suggestions raised: 1. Give better suggestions to user, e.g. if user enters 'Artist1; ' and starts typing 'Art', suggestions like 'Artist1' and 'Artist2' will be given, instead of 'Artist1; Artist2' as in a standard drop-down. (I think that this would be a nice addition) 2. Add some button (like '...') that would open an editor for fields with mutliple values. This could be useful, but is possibly unnecessarily complex and a little clumsy. 3. A drop-down with checkboxes for selecting artists. Could be, but again, probably a little harder to use. 4. Anything else? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I think that the current approach of using ';' is fine for now and that there's no clear need to support multiple separators (input or output). 1. This could be useful. i.e. adding support for multiple dropdowns within a single form. Each time the user clicks ';' a new dropdown would appear. 2. i agree we should hold off on this for now 3. For the purposes of Searching, I agree that this is useful IFF the search is for Artist or Genre _equals_ x. Note that typing should still move the dropdows to the correct location of the artist list. |
|
|
Assigning to Petr to check out if/how could we implement 1. |
|
|
Another possible approach is to use a dropdown list with checkboxes. i.e. -tracks are listed as Genre1; Genre2; Genre3 -when the user starts typing, the dropdown dialog opens with a list of Genres preceded by checkboxes + a scrollbar. e.g. [ ] Genre1 ^ [x] Genre2 | [ ] Genre3 | [x] Genre4 | [ ] Genre5 | ... v ... Typing would cause the scrollbar to move to the relevant Genre. Pressing spacebar or clicking the checkbox would cause the Genre to be added. BUT the big problem with this approach is that there's no way to choose the order of the Genres, and the order of Genres is relevant if we decide to treat the first genre as special (e.g. for the purposes of syncing). We'd need to figure out a way around this... |
|
|
Item 1 is implemented. When user will type ; character and then types next value in the field, an auto-completion functionality will do his job (same as when user is typing first value). |
|
|
When auto-organizing it would be nice to have a function which makes ";" relevant when dealing with folder/file-names. For example: "Alison Krauss; Robert plant" in <Artist> tag would be possible to sort like "Alison Krauss & Robert Plant". This is because ";" isn't supported in the file/folder-names. Assigning to Rusty for input. |
|
|
I don't think it's necessary to add anything, in case of filenames users can use mask functions (like $Replace()) to do this stuff. |
|
|
verified 1223 |
