Also there are a few inconsistencies between the new field popup and the edit field popup:
Note editing a separator entry allows to change the name/field/value; while the new field popup have those options greyed out for _separator field.
I think this bug is not new, since checking my field tags I renamed one of them to "---------------------------" on purpose to create a separator a long time ago XD It's just that checking it now again I noticed it.
I just had to learn my lesson and found the following in the documentation:
The special field name ... _SEPARATOR to add a separator that creates a new row.
So you would have to use the _SEPARATOR for a field that is smaller than "large" to avoid that other, smaller fields appear in the same line.
The _SEPARATOR does not include a visible line.
So I would say that it works as intended.
Or in your case: as the previous field DESCRIPTION is already large, there is no further separation (i.e. new line) possible.
Try the _SEPARATOR behind COMPILATION and see whether it works.
My complains are not about the new line not working.
While I thought the same, why adding a name field in such case? That field should do exactly what I ask for; if you leave it blank it just creates a new line (right) but if you modify it, the text should be displayed. Otherwise just don't allow editing the name field.
To configure a field, you need to provide a Name, which is the label text that appears on the Tag Panel. The Field is the actual tag-field name. This can be any of the pre-defined fields chosen from the drop-down list, e.g., ISRC or a custom user-defined field identifier like MYCUSTOMFIELD1.
Also note there is no place at the docs stating that _Separator entry doesn't follow the 'name' behavior. In fact it's stated that any entry will use the name set.
In either case this is a bug, since all entries on tag panel show the Name field. Separator is the only one which doesn't but allows to edit the name (?). Either make it non editable (and warn about it on the docs) or use the set name to behave as a named separator, but current behavior doesn't follow a clear logic or the docs.
In other words:
Adding a separator with no name should be displayed as:
Adding a separator with name should be displayed as (edited in Photoshop):
So this means that the separator is actually working.
I just checked in 3.18b:
as long as you have not set the "Field" to _SEPARATOR, you can edit all the other properties - which I think is good GUI style as the user should not be forced to obey a specific order when entering data.
Yet, as soon as you select _SEPARATOR, most of the the other properties get disabled.
Anything that you entered so far is kept until you save the modification - it could be that you selected _SEPARATOR accidentally. And as soon as you select a different field, the other properties are enabled again.
After saving, the entry with _SEPARATOR as field is shown as "Separator" (or in my German version as "Trennzeichen") in the list of tag panel objects.
So, I still think that the behaviour is OK and even fairly close to that what you intend to get.
And if that is true then it looks to me like a documentation flaw.
This still does not mean that the separator itself does not work.
IMHO it does that what has been described: it inserts a new line in the tag panel.
Your original statement was
Which is an observation due to the previous large field.
So the original title of the thread "Separators not working on Tag panel" should really be "Documentation does not show the full behaviour when using _SEPARATOR for tag panel".
What I am wondering about:
Do you get the new line when the previous object does not cover the full width of the tag panel?
And if so, does the current behaviour hinder you to insert separators?
This conversation is going in circles... have pointed to at least 3 erratic behaviors and things not working as they should be; I don't think the "relevant" topic here is if the thread should be named "Separators don't work properly" instead of "separators don't work" or any other way. You are focusing again and again on a different point than my report and every one my replies. But there you go, I edited the title.
And they clearly don't work neither following the documentation nor as they were supposed to be designed. There you got the bug report, if someone cares about it, since there is clearly something wrong. Best regards.
The separator function is used to force the tag panel to move the fields following it to start from the below the previous one.
While the name field for the separator does not display on the tag panel itself, I find it helpful to use in the options to indicate what the below grouping it is intended for. This is useful when using more than one separator.
Name arbitrarily changed when editing the separator, even if you don't edit the field name. Shown on gif.
Name not being editable when creating entry, but being editable afterwards. Shown on gif.
Name not being displayed when the documentation says otherwise. Quoted the docs.
I know what's the use of the separator, or the name being "useful" on the options panel, but in any case it's still not working as expected. And there are at least 3 bugs here.
Name should not be automatically edited with a blank value.
2.a Name should be editable at all steps. That includes at creation.
2.b Name should not be editable at a later point since it's greyed out when creating a separator.
3.a The docs must be updated to warn about separator not following the global tag panel behavior. (and then Name being editable should be re-though)
3.b The separator should display the name on the tags panel.