REQUEST: Tag Panel new Size Of Field - micro

[Zerow]

@Quisquose

[...] a track number (usually a maximum of 2 characters)

Some people might use 3 digits, with the first denoting the disc. Or 1 letter + 2 numbers. And what about when the set has more numbers than just 99?

I for example use a custom approach, that often goes [extends] up to 7 characters; with the possibility of going even further [for numbering sets composed of unlimited number of tracks]

@Quisquose

[...]
more control so that you can specify the size yourself.

Maybe instead of operating within a fixed set of 4-6 sizes, we could have the ability to operate with percentages; similar to what can be done in HTML in regards to cells / tables?

If agree that the original / old size is 100%, then we could go up and down by something like 10%? Up to whatever we want [as somebody might be using a 32:9 monitor], and down to as little as 10% [being the value of the step]?

@Quisquose

Additionally, I find the naming confusing and inconsistent. "Normal" is not a size,
[...]
the fact that "smaller" is bigger than "small" makes no sense. Small > Smaller > Smallest. Big > Bigger > Biggest.

I also elaborated on that:

Tag Panel: horizontal layout improvements to tag fields

I know now what is wrong... or "wrong" I think that this either a case of semantics and / or nor being a native English speaker, which that latter one being true for me and [I assume] also for @Florian: SMALL in less than whatever you define as being NORMAL. But SMALL also means more of something than the SMALLER amount of it So how abut changing the order of names or even names themselves to avoid such confusions? Currently it is Normal > Smaller > Small > Multiline And so N…

@LyricsLover

This was fixed in
2.90d
[...]

That is good to know

@Quisquose

Finally, the change in font has made all my tag field titles larger, so now I have to widen the tag panel (and reduce precious track-list column width space) to be able to fit the same amount of information that I used to have in my previous Mp3tag version.
[...]

I had not such problem. I still use vertical Tag Panel with minimum width. Your problem depends most likely on these factors:

• resolution set in the OS
• size of font set in the OS
• size of borders [and others elements?] set in the OS

@LaurenBacall

@Quisquose

The same goes for the Year field which will always only ever be 4 characters (there is a separate Date field for people who want a full date)

From what I've read here the Year field supports the full timestamp, and for specifically for ID3v2.3 is mapped to Date (being discontinued in v2.4). Vorbis from what I've read also uses the same ISO standard timestamp format.

Since discovering that I always use the full timestamp where available in Mp3Tag's Year field. Just thought I'd share my use for comparison.

And some people might use YEAR for something different, for whatever reason

I for example am forced to use the COMMENT tag field for additional year related info [the year of first recording and / or composing of a given track], because Advanced Title Formatting in Winamp will display data from COMMENT- but will not display a legite DATE tag field or SOME-MADE-UP-BE-ME-FIELD

And there are also issue associated with using on a daily basis different audio formats [[X] Can't copy some unusual TRACK tags from MP3 / FLAC to WMA, APE files problem], which may force the user the adapt one of the fields for some other usage