1166 "Edit Properties for Multiple Tracks" blank v mixed

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: 1166 "Edit Properties for Multiple Tracks" blank v mixed

Re: 1166 "Edit Properties for Multiple Tracks" blank v mixed

by Bex » Sat Jan 17, 2009 11:17 am

Re: 1166 "Edit Properties for Multiple Tracks" blank v

by MM3 monkey » Sat Jan 17, 2009 8:06 am

I've just finally mentioned this elsewhere (here's the link: http://www.mediamonkey.com/forum/viewto ... 80#p186580 ) but it's been a glaring issue for a long time.

It would be good if this could be given priority, unless it's really a difficult thing to implement. It would be so helpful for all of the custom fields and ISRC and publisher and encoder; they are all used frequently and it would make such a difference to be able to tell the difference between MIXED and ALL EMPTY, so you don't end up overwriting fields.

A greyed-out checkbox would work almost as well as greying out the field itself - like the checkbox state MediaMonkey already uses in the "Add/Rescan Tracks to the Library ..." dialogue when you have selected only some of a group of subfolders.

Pretty please!!

by chrisjj » Mon May 12, 2008 1:56 pm

MoDementia wrote:I would hope for a greyed indication "Multiple Values" perhaps in these fields.
That get's my vote.

by MoDementia » Thu May 08, 2008 8:05 pm

Ah I forgot to add this , thanks

I would hope for a greyed indication "Multiple Values" perhaps in these fields.

by Teknojnky » Thu May 08, 2008 8:03 pm

Good idea, I suggest greying out the input field to indicate there is data there but non-matching. I think many other multiple selection type dialogs/programs do this type of thing.

1166 "Edit Properties for Multiple Tracks" blank v mixed

by chrisjj » Thu May 08, 2008 8:01 pm

Could "Edit Properties for Multiple Tracks" controls please visually distinguish the 'mixed value' state, which currently appears blank just as it does for a genuine blank value :)

This is such an obvious thing that I wonder if I've overlooked something.

What do others think?

Top