@Brecht Van Lommel (brecht) : Doing it by removing the name of properties is not ok, all properties must have valid names

Yes, I realized that was dumb when I found another multi-column list (Languages).
And then took that out before I noticed you mention it. LOL

This is definitely an improvement for cases where we have overflowing columns, as the last image shows.

If the technical side is ok, I think we should make this change.

I like the changes here too. I think Campbell would be the one to check on the code side though.

Totally forgot about this one too. +1 for sure!

I like the line dividing the categories, would this also apply do the Modifiers list? (this is master, couldn't test this patch yet)

@Pablo Vazquez (pablovazquez) - ...would this also apply do the Modifiers list? (this is master, couldn't test this patch yet)

No, that list is made in some other way (doesn't use ui_def_but_rna__menu). This change makes the other lists more like the Modifier list since it it removes the "Title" if there are categories. So, for example removing that "Editor Type" we see the top of that list.

But yes, we'd just have to add that divider line under the categories in the Modifiers list and they would look the same. Now I just have to find that thing...

You know what, I'm always wondering why the "scripting" column comes first than the "data" column (left to right)... I'd swap those two sections and make the "scripting" the last one, since it's the least used section, I think?
But hey, that's just me... lol...

In D5135#228816, @Harley Acheson (harley) wrote:

@Pablo Vazquez (pablovazquez) - Added a rule inside uiItemsFullEnumO_items() so that the "Modifiers List" looks the same as the others:

Great, thanks! To me this is good to go from the UI side of things.

In D5135#228819, @TheRedWaxPolice (TheRedWaxPolice) wrote:

But hey, that's just me... lol...

No, it's not just you.

@TheRedWaxPolice (TheRedWaxPolice) ... I'd swap those two sections and make the "scripting" the last one

Yes, me too. But there’s no way I’d touch that with a ten foot pole as the “muscle memory” crowd would have me in a pillory.

In D5135#229233, @Harley Acheson (harley) wrote:

Yes, me too. But there’s no way I’d touch that with a ten foot pole as the “muscle memory” crowd would have me in a pillory.

I doubt people will even notice it... hehehe..

@Alexander Gavrilov (angavrilov) - Is it intentional that menus without named categories completely lose the capability to have simple separators?

No, it is an unintentional change from what is seen on the left to what we now see on the right:

I'll investigate and/or make a bug report.

I already tested locally that this fixes it before even commenting here:

   uiItemS(column);
 }
+else if (categories == 0) {
+  uiItemS(column);
+}

So it's 100% caused by this patch. If you don't want to forbid anonymous separators when there are categories, you can fix this even easier by just moving the call outside of if (item->name).

@Alexander Gavrilov (angavrilov) - If you don't want to forbid anonymous separators when there are categories...

The intent of this particular patch was never to stop adding anonymous separators so I can't think of why to not allow them if there are categories. I mean it would look dumb but that's not up to me.

Wouldn't the fix just be this though? Or am I missing some detail here?

     if (!item->identifier[0]) {
       if (item->name) {
         if (item->icon) {
           uiItemL(column, item->name, item->icon);
         }
         else {
           /* Do not use uiItemL here, as our root layout is a menu one,
            * it will add a fake blank icon! */
           uiDefBut(block,
                    UI_BTYPE_LABEL,
                    0,
                    item->name,
                    0,
                    0,
                    UI_UNIT_X * 5,
                    UI_UNIT_Y,
                    NULL,
                    0.0,
                    0.0,
                    0,
                    0,
                    "");
         }
-        uiItemS(column);
       }
+      uiItemS(column);
     }
     else {

In D5135#234632, @Harley Acheson (harley) wrote:

Wouldn't the fix just be this though? Or am I missing some detail here?

That's what I meant by 'move outside the if' :) I just didn't really look through the other code to see if it would interfere with categories in any way and tested a conservative fix.

@Alexander Gavrilov (angavrilov) - That's what I meant by 'move outside the if' :)

Yes, sorry for being pedantic but I totally missed this type of menu with anonymous separators so want to make sure that I'm not missing anything else. LOL. I really do appreciate your help.