# REQUEST: Tag Panel new Size Of Field - micro
**URL:** https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525
**Category:** General Discussion
**Created:** [November 10, 2018, 1:55pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525 "2018-11-10T13:55:47Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [November 10, 2018, 1:55pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/1 "2018-11-10T13:55:47Z")
Under the
**Tools \> Options \> Tag Panel \> Tag Panel [area] \> Edit Field [icon] \> Size Of Field**
we can choose now the size of each and every field, which is very helpful and I thin was a long awaited feature. And so we have:
- Normal
- Smaller
- Small
- Multiline
[which is, on the side note, kind of confusing: [Tag Panel: horizontal layout improvements to tag fields](https://community.mp3tag.de/t/tag-panel-horizontal-layout-improvements-to-tag-fields/40873/29)]
How about a new one: **micro**?
It would be even smaller than the current smallest one available. For example it could be utilized for [consisting hypothetically of only 2 character] fields like TRACK or for fields [consisting hypothetically of only 1 character] like SIDE [assuming you denote sides of tapes / vinyls]. Switching some of the fields to micro sizes could further save space for the user, thus give that user the ability to see even more of tag fields and files on one screen [without the need for scrolling]
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [November 10, 2018, 2:17pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/2 "2018-11-10T14:17:07Z")
+1
I suggested that here:
> [@Tagpanel: Weitere Grösse "sehr klein"? / Coveranzeige frei anordnen?](https://community.mp3tag.de/t/tagpanel-weitere-groesse-sehr-klein-coveranzeige-frei-anordnen/42119):
>
> Die Möglichkeit zur Grössenangabe für einzelne Felder im Tagpanel finde ich sehr gelungen! Was mir noch fehlt, ist eine weitere Grösse "sehr klein" (oder so ähnlich benannt). Diese Grössenangabe könnte man verwenden, um Felder mit sehr wenig Inhalt wie "Jahr", "Track" oder "Disc-Nummer" noch platzsparender nebeinander anordnen zu können: Zudem wäre es sehr praktisch, wenn man auch die Cover-Anzeige beliebig in der Reihenfolge ändern könnte und nicht nur fix als letztes Fel…
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [November 10, 2018, 2:23pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/3 "2018-11-10T14:23:19Z")
I could use that too for the content (I have some self-defined 1 character fields) but I have no tag-name that is short enough.😉
---
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [November 10, 2018, 2:35pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/4 "2018-11-10T14:35:14Z")
But even the shortest field would still require the additional space for the triangle icon. So you could still use more that one letter to describe such field
And even if you would only have as little space for describing a given micro field as containing only 1 or 2 characters- then you could use something other than letters and / or numbers. Here are some examples: [https://en.wikipedia.org/wiki/Geometric\_Shapes](https://en.wikipedia.org/wiki/Geometric_Shapes), [https://en.wikipedia.org/wiki/Block\_Elements](https://en.wikipedia.org/wiki/Block_Elements)
It is your version of Mp3tag with your settings and those would be descriptions and not even the `%ACTUAL_NAMES_OF_TAG_FIELDS%` - so you needn't to worry abut using something that anyone else will not understand
---
### Author:  [@Quisquose](https://community.mp3tag.de/u/Quisquose)
#### Post date: [November 16, 2018, 11:52am UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/5 "2018-11-16T11:52:13Z")
I came here to post **exactly** the same thing that you did!
I just upgraded to v2.90 from v2.78 (.... yeah, if it ain't broke don' fix it!) and while I like and very much appreciate the new features, stability and bug fixes, the "field size" issue instantly annoyed me within seconds of the install completing. It's like coming home from work and finding that someone has moved your furniture around - lol.
In v2.78 the 'Genre' field in the Tag Panel was about 2.5 times the size of the 'Year' and 'Track' number panel. I have no idea why all the fields have now been made the same size. When is a track number (usually a maximum of 2 characters) ever going to require the same amount of space as a field which describes musical genres? 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). So it seems a strange choice to limit the Genre field so that most of the text it cut off, just to give a bunch of space to two fields that don't need it.
Like other posters here, I would very much like to see a greater range of field sizes, or more control so that you can specify the size yourself.
Additionally, I find the naming confusing and inconsistent. "Normal" is _not_ a size, and gives no indication of how big it will be or how its size compares to other fields. "Normal" implies to me "standard single line" instead of "Multi-line", but it says nothing about its size. I also find the fact that "smaller" is bigger than "small" makes no sense. Small \> Smaller \> Smallest. Big \> Bigger \> Biggest.
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.
Luckily, all these issues are really trivial to fix, and they would really improve the user experience considerably, so hopefully Florian would be prepared to make a few adjustments.
I'd also like a checkbox option on the Tag Panel settings dialog to lock the panel selection so that you when you right-click there is only a menu item to go to the Tag Panel configuration dialog to unlock it (if you want to make changes). For those people who change their tag panels constantly, then obviously they would not choose to select the "lock tag panel fields" option, which means that could continue enable and disable individual fields by right-clicking the the panel, just as you can now.
Thanks to the developer for all his hard work fixing bugs. I read the Version History list and a lot has happened since v2.78. 😀
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [November 16, 2018, 1:15pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/6 "2018-11-16T13:15:17Z")
> [@Quisquose](#):
>
> Additionally, I find the naming confusing and inconsistent. "Normal" is _not_ a size, and gives no indication of how big it will be or how its size compares to other fields. "Normal" implies to me "standard single line" instead of "Multi-line", but it says nothing about its size. I also find the fact that "smaller" is bigger than "small" makes no sense. Small \> Smaller \> Smallest. Big \> Bigger \> Biggest.
This was fixed in
**2.90d** (2018-11-12) [mp3tagv290dsetup.exe](https://download.mp3tag.de/mp3tagv290dsetup.exe)
...
- CHG: renamed tag-panel field sizes to large, medium, and small. ([#40873](https://community.mp3tag.de/t/40873))
> [@Quisquose](#):
>
> see a greater range of field sizes, or more control so that you can specify the size yourself.
THIS point is still on the wishlist 😉🌲
---
### Author:  [@LaurenBacall](https://community.mp3tag.de/u/LaurenBacall)
#### Post date: [November 17, 2018, 2:43pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/7 "2018-11-17T14:43:14Z")
> [@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](https://community.mp3tag.de/t/date-vs-year/9819/4), 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.
---
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [November 17, 2018, 5:04pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/8 "2018-11-17T17:04:02Z")
> [@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](https://community.mp3tag.de/t/tag-panel-horizontal-layout-improvements-to-tag-fields/40873/29):
>
> 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](https://community.mp3tag.de/t/date-vs-year/9819/4), 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](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714), [APE files problem](https://community.mp3tag.de/t/ape-files-problem/17672)], which may force the user the adapt one of the fields for some other usage
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [November 17, 2018, 9:28pm UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/9 "2018-11-17T21:28:57Z")
All the discussions about which field should or could be how long is of secondary importance. Everyone can choose the size for every tag.
There should just be at least one additional "micro" size (about half the size of small).
If we can adjust the size in pixels or percent it would be great too.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [January 2, 2019, 10:29am UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/10 "2019-01-02T10:29:49Z")
I've added the Tag-Panel field size _Smaller_ (i.e., smaller than _Small_) with [Mp3tag v2.91c](https://community.mp3tag.de/t/455).
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [February 1, 2019, 10:29am UTC](https://community.mp3tag.de/t/request-tag-panel-new-size-of-field-micro/43525/11 "2019-02-01T10:29:50Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.