What about a dropdown menus with each select able like with check marks or something

Also the modifier is not listed in alphabetical order in the list

Order in list is fixed…

As for UI, any suggestion is for sure welcomed, but beware, there are several constraints to respect here:

• Settings should be grouped by elem types (verts/edges/etc.)
• Some data types have extra settings, and it should be blatant in UI that they are specific/related to that data type (vgroups, vcols and UVs - and in future skeys too, and possibly others).

We spent a bit of time on this with Campbell, and could not find anything better than what’s currently in master.

PS: not quite sure we need a design task for all and every minor subject like this? Else we'll end up with tons of those…

I am glad we have a design task for this, the current state is definitely not acceptable for the final 2.74 release, no offense, but that's just bad. :/

I’m about to close this, seems nobody has alternative propositions, we do not need dangling Design tasks like that, esp. not on such details…

Dammit, forgot to press submit again......
@Bastien Montagne (mont29), I agree this is complicated but let's at least do some brainstorming to see what could be done to improve this. And yeah, IMO we need design tasks for minor but really special things like this, cause where should we discuss this else? We could do this in similar tasks like T41700, but then *someone* would come and say that this is off topic and makes the task hard to follow ;)
I see your concern about having too many unorganized design tasks everywhere, but I think that's not too bad. This way, at least we get the chance to discuss all the small little things in detail and we allow users to join in as well! Although I totally agree that we already have too many "resting" UI design tasks open...

Anyway, the first proposal I'd make is to use checkboxes in menus for the enum toggles on the left (like @Aaron Carlisle (Blendify) suggested). We use a similar principle in other places, such as the Timeline Playback menu. I don't see a problem with that, should work with the points mentioned by Bastien as well.

I do not like that proposal, for at least two reasons:

1. Checkboxes in enum menus are much harder to reach than big plane buttons of expanded enums. They are OK for general options you do not tweak often, but for main feature of a modifier… Besides, we already have checkboxes to enable/disable a whole set of data types.
2. How do you handle 'multi layers' data like vgroups or UVs in this case? You have to show those options one way or the other - conveying the fact that they are specific to a given data type.

One improvement is to make each collapsible like in other menus. also maybe you can have other advanced options for some maybe?