View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017973 | MMW 5 | Install/Config | public | 2021-06-01 20:21 | 2021-10-28 22:37 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0.1 | ||||
| Target Version | 5.0.2 | Fixed in Version | 5.0.2 | ||
| Summary | 0017973: Multi-Value Separator setting allows entry of multiple characters | ||||
| Description | 1) You can fill in multiple characters in the separator setting (Tools > Options > Fields). As only a single character is allowed the field itself should not be able to take additional characters. 2) Using the drop-down auto-complete it adds the selected value to the existing separator instead of replacing it. 3) An option to allow for a leading space would be a good addition. For example using ; a space in front isn't needed, but using | as separator it would look better as value1 | value2 instead of value1| value2. This could be a sub-option. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2512 | ||||
|
|
2) fixed in build 2500, it was bug. I am not sure about the rest, currently we support space(s) + character + space(s), the suggested solution would decrease variability. I think current solution is ok, only we could automatically adjust value after entering not supported combination (e.g. with two nonspace characters). Rusty, what do you think? I.e. after entering ' Xx ' value would be auto-adjusted to ' X ' etc., currently it is auto-adjusted later and not clearly visible to user. |
|
|
Or we can add 2 checkboxes for setting leading space and trailing space. But for me it is unnecessarily too many controls to one simple setting, which users use only rarely. I would leave it as it is. |
|
|
I'm not sure if any changes are needed, since: 1) The reason for allowing > 1 character is to configure how such fields are _displayed_, i.e. if the user chooses: - '|' then fields are shown as artist1|artist2 - ' | ' then fields are shown as artist1 | artist2 When the user enters the splitting character in a field that spacing is ignored. i.e. if the splitter is configured as ' | ' then whether the user enters artist1|artist2 OR artist1 |artist2 OR artist1| artist2, MM will display the field as artist1 | artist2 So the only change that I'd suggest would be to only allow a single splitter character + (optionally) the ' ' character (before and/or after) ? 3) As described above, such an option doesn't seem to be required as it's already implemented (the user just has to enter ' | ' as the splitter. 4) I think that the issues/confusion raised by LL is due to the fact that the The tooltip implies that only a single character is used. We might want to change it as indicated: This specifies what character is used to denote multiple values within a single field (e.g. Rock;Folk). --> This specifies what character is used to enter multiple values within a single field (e.g. Rock;Folk) and spacing for how the values are displayed. LL, if you agree, please re-assign to Michal for feedback. |
|
|
1) That works for me, it should only allow input that will actually be used: 1 ' |- ' is allowed as input, but only ' | ' is displayed 2 '; ' is allowed, but only 1 space is displayed 4) Tooltip is a good idea 5) It indicates a restart is required, none is offered when changing this setting. Also it seems to work as expected without restart, so is it really required? |
|
|
Fixed in build 2509. Restart note removed. Value is auto-adjusted after editing to not contain unsupported value (changing it during editing would be uncomfortable). |
|
|
1) 3 ';- ' is changed to ' ;' trailing space becomes leading space 4 There is no feedback to user that the entered value is incorrect. It would be better if there was feedback, and not just silent change. So either A) a prompt that entered value is incorrect, only single separating character allowed, please fix B) a prompt that only single separating character allowed, additional characters have been removed C) Field turns red, with label next to it that multiple separating characters detected, please fix 4) I'm not sure that the tooltip really clarifies that a single separator character is allowed. 5) Fixed |
|
|
4) I would not complicate things for such simple setting (MM4 also changes used separator silently). What about simple toast message of type B? I did not used it yet, as we do not have such strings, but if this wording is ok, I can add it. |
|
|
3) fixed in build 2510. |
|
|
1) I agree that it's overkill--afaik we haven't had many complaints/confusion about this (and MM5 already improves this over MM4) 4) How about the following tooltip: This specifies a single character used to enter multiple values within a field (e.g. Rock;Folk). Spaces determine how the character is displayed. |
|
|
4) That works much better. |
|
|
Tooltip wording fixed in build 2512. |
|
|
Verified on 2512 |
