View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007223 | MMW v4 | Framework: Scripts/Extensions | public | 2011-01-22 21:33 | 2011-04-11 18:10 |
| Reporter | zvezdan | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Target Version | 4.1 | ||||
| Summary | 0007223: Several new custom fields in Songs table that will not be connected to any tags needed | ||||
| Description | Those new custom fields should be accessible in masks like any already supported field, e.g. existing Custom fields. In such case we could use the new Summary column to display such field with some data that are not and should not be stored in files as tags. For example, there is request for my Queue List script to allow display of column in Now Playing panel with the serial number of tracks from the mentioned list. One user suggested using some Custom field for that purpose, but I don't like idea to store such temporary number to tags in files. So, I could populate one new proposed field with such data and use Summary column to display that field. Another example which comes to my mind is Bex's script which displays used playlists for every track in the tracklist. IIRC, he is using some Custom field to store that information, but I bet that he would prefer to use some new field for that purpose which would not be assigned to any tag since that information is only needed inside of the program. Many users in Wishlist forum suggested adding some new fields that also don't need to be stored in any tag, e.g. Date when file is created (which could be different from Date when file is modified). If you add fields not related to tags which could be used in Summary field, the mentioned problem could be easily resolved. Several (at least 5) new custom fields are recommended because some user may want to install different scripts which wants to store such data. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I see Zvezdan point. Scripters use Custom Fields to Store Additional Data Not available in maybe we should consider making some sort of ability to make Additiona Database Table named "Custom<CustomName>" that can be used by Scripters it will be tied to SongID from Songs Table and structure should be limited or defined withing Actual Script. |
|
|
Reminder sent to: jiri, petr, rusty Jiri, can you evaluate for MM 4.1. I think that this should work and it should not make speed problems with MM. Let me know if you need some small Script Example. |
|
|
Zvezdan, I haven't tested fully but from what I see there is possibility to Create Tables in MM.DB using MM SQL script functions? |
|
|
Yes, there is a possibility to create tables in scripts and I am already using that in some of my scripts. However, it seems that you are missing a point and I would try to explain it better. The Now Playing panel from MM4 has the Summary column and I want to use that column in my scripts. That column displays data using masks similar to Auto-organize so it could display only those fields that has corresponding tags, i.e. <Artist>, <Album>, <Title> and so on. I want a possibility to display in Summary column some field which is not stored in tags, but only in database. It doesn't matter in which table would be located that new field(s). In fact, I cannot see any reason to store such fields into another table since there is not any one-to-many relations between tables. |
