Elimanting the "#" in the "Track #"
Moderator: Gurus
Elimanting the "#" in the "Track #"
This is a very minor point and is only a suggestion but I would like to see the "#" (number symbol) in "Track #" removed to give more overall space in the window where you have (Title, Artist, etc.). It should just say "Track" since this area only, at the most, uses 2 numbers, so as to minimize it the least possible. MediaMonkey is by far the best out there. thanks
Re: Elimanting the "#" in the "Track #"
Tracks from multidisk collections most of the times are marked like 101 (1st track of 1st CD) or 205(5th track of 2nd CD). So as you can see this field should be capable of handling 3 digit numbers...Rayi23 wrote:...since this area only, at the most, uses 2 numbers, so as to minimize it the least possible...
I think it's just the fact that to make the column width right for 3 digits the title becomes "Tr..." which means there would probably be room for "Track", but not for "Track #". The " #" is fairly pointless as I think everyone would know that "Track" meant the track number.
Download my scripts at my own MediaMonkey fansite.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
I think the # should stay as it helps novice users identify the purpose of the field more easy.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
agree
I agree with Rayi23.
In my 10+ years of designing applications, I've found repeatedly that using "No." or "#" is always understood by the user when the value of the field is numeric. As a result, people find it unnecessary and often ask to have it removed. In a few cases, I found that people would rather have nothing or have "Number" spelled out. Not what I would've expected, but hey, that's the client's desire. (And I really have had the classic "stupid user" type of clients... you know, the kind that asks if the CD-Rom tray is a coffee cup holder.)
So, when it comes to issues of space, and particularly on things where clutter is to be considered (such as in grid headers), it probably is the best design to drop the "#".
Also, if there is validity to newbs being helped by it... the moment they realize what that column is, is the moment that they no longer need the "#" indicator. I'm betting that they could figure it out without the hash mark and that would only take them at worst 5 seconds longer the first time only.
In my 10+ years of designing applications, I've found repeatedly that using "No." or "#" is always understood by the user when the value of the field is numeric. As a result, people find it unnecessary and often ask to have it removed. In a few cases, I found that people would rather have nothing or have "Number" spelled out. Not what I would've expected, but hey, that's the client's desire. (And I really have had the classic "stupid user" type of clients... you know, the kind that asks if the CD-Rom tray is a coffee cup holder.)
So, when it comes to issues of space, and particularly on things where clutter is to be considered (such as in grid headers), it probably is the best design to drop the "#".
Also, if there is validity to newbs being helped by it... the moment they realize what that column is, is the moment that they no longer need the "#" indicator. I'm betting that they could figure it out without the hash mark and that would only take them at worst 5 seconds longer the first time only.