View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000554 | MMW v4 | Properties/Auto-Tools | public | 2003-07-08 19:43 | 2010-10-25 15:56 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.3 | ||||
| Summary | 0000554: Ability to rename Custom fields | ||||
| Description | It would be nice if there was a simple means of renaming the Custom1, Custom2, etc. fields to fields that are more meaningful to the user. | ||||
| Additional Information | Note: this functionality may also affect the strategy we take wrt to support of classical music (since users could theoretically rename a number of fields in this manner to better fit classical music). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 797 | ||||
|
|
Fixed in build 771. - It's possible to configure Custom field names in Appearance sheet of Options dialog now. (MM restart is needed in order to update all instances of the strings) |
|
|
In terms of location within the configuration panel, it would make much more sense to place this in: -Library --Tags and Playlists --File Monitor --Custom Fields <------- .. |
|
|
Fixed in build 797. - Included for 2.3 release. - They don't have their own sheet yet in order to not have to many sheets, can be adjusted in the future. |
