by Mizery_Made » Tue Sep 06, 2011 2:46 am
I know that this is a subject that has been discussed here and there over the years, but I don't think it's something that can hurt to bring up again. We're already supplied with custom fields, which is nice as it allows people a place to stick misc information to suit their own needs. However, I think it would also be useful to have available a small group (maybe 3, or 5 to coincide with the number of custom fields?) of check boxes which too can be given a custom name.
The reason being, while not everyone does, I know there are some that will fill up a custom field with a "two-state" type marker. For instance, I've been using Custom 1 for quite some time to denote whether I have rated that album or not. For years, I would simply leave the majority of my tracks unrated while simply giving those that I really liked a 5-star rating. Over time, this system seemed pretty flawed and I got to where I would go through an album when I got it and rate each track, occassionally going through older albums to give them the same treatment. So, I've used my "Rated" custom field to separate the "legitament ratings" from the "lazy ratings" if you will. I supposed I could just clear out all the "lazy ratings" which would negate the need for a "rated" field (as then anything with a rating would have been "rated" but that's beside the point.
Fact remains that some people desire something like this, and others may find it useful down the road. I know that most frequently there has been a request for one check box to work similarly to that of iTunes where only checked tracks would be played/synced. One could be given for this, or you could supply an option to choose one of the Custom check boxes to function like this. *Shrugs*
Having some check boxes though would clear up three of my Custom Fields, as they each currently have two-state information in them to denoted "Rated", "Sync" and "Duplicate/Snippet".
I seems pretty easy to implement though. Being a two-state field wouldn't inflate the database much, as you would just need one value saved for each "0/1" for instance to indicate "off/on" respectively. You could also use a similar logic to that of the present Custom fields when it comes to saving them to the tags of files. Plus again, only a 1 value field would be necessary to represent the two states.
I know that this is a subject that has been discussed here and there over the years, but I don't think it's something that can hurt to bring up again. We're already supplied with custom fields, which is nice as it allows people a place to stick misc information to suit their own needs. However, I think it would also be useful to have available a small group (maybe 3, or 5 to coincide with the number of custom fields?) of check boxes which too can be given a custom name.
The reason being, while not everyone does, I know there are some that will fill up a custom field with a "two-state" type marker. For instance, I've been using Custom 1 for quite some time to denote whether I have rated that album or not. For years, I would simply leave the majority of my tracks unrated while simply giving those that I really liked a 5-star rating. Over time, this system seemed pretty flawed and I got to where I would go through an album when I got it and rate each track, occassionally going through older albums to give them the same treatment. So, I've used my "Rated" custom field to separate the "legitament ratings" from the "lazy ratings" if you will. I supposed I could just clear out all the "lazy ratings" which would negate the need for a "rated" field (as then anything with a rating would have been "rated" but that's beside the point.
Fact remains that some people desire something like this, and others may find it useful down the road. I know that most frequently there has been a request for one check box to work similarly to that of iTunes where only checked tracks would be played/synced. One could be given for this, or you could supply an option to choose one of the Custom check boxes to function like this. *Shrugs*
Having some check boxes though would clear up three of my Custom Fields, as they each currently have two-state information in them to denoted "Rated", "Sync" and "Duplicate/Snippet".
I seems pretty easy to implement though. Being a two-state field wouldn't inflate the database much, as you would just need one value saved for each "0/1" for instance to indicate "off/on" respectively. You could also use a similar logic to that of the present Custom fields when it comes to saving them to the tags of files. Plus again, only a 1 value field would be necessary to represent the two states.