Items automatically sorted in the presets

[severin.menard]

values_sort="true|false" exists, but there is no items_sort="true|false" to maintain a desired order in a group, regardless of the chosen locale language.

[stoecker]

There is a "Sort presets menu alphabetically" for that in settings: Help/Preferences/TaggingPresetPreference

If that's not what you search please explain better.

[severin.menard]

I meant within the items in a preset group, not within the presets

[stoecker]

This options sorts menu as well as items. As said, when that's not enough explain better.

[severin.menard]

"Sort presets menu alphabetically" is a general setting for all the presets in the menu. I am talking about not sorting within a specific preset I am creating.

You can see below that "Roof material" is on top in the EN version, while "Matériaux du toit" (FR translation) is at the bottom. This is why I was looking for items_sort="true|false" which would do what values_sort="true|false does very well for the values inside a combo box.

---

[stoecker]

That's not supported and also makes no sense. The menu entry is either pre-sorted logically (with whatever logic the preset author thinks useful) or user defined alphabetically. A mix of these two would be awful from a UI perspective.

Sorting is default nowadays as experience showed that's the better choice.

[severin.menard]

It is not supported, but I disagree that it makes no sense. In the case of my preset, "Visible damage..." is the most important form, so it would definitely make sense to be on top. I may add other complementary forms in the future, and I would prefer the most important one to be on top. I can also get around this limitation by adding a "0" before "Visible".

[stoecker]

From a point of view of a preset editor: Maybe.

But from a user perspective an UI should be consistent. If it is sorted, it should be sorted everywhere, otherwise people wont find or overlook stuff. It's already complicated enough as it is now.

We started with logically arranged presets (i.e. streets by class), but over the time the alphabetical sorting overrode this.

Getting different requirements into one software always means making compromises. No way around that.

[severin.menard]

So, why is there a values_sort="true|false parameter? :)

[stoecker]

That's inside the preset. Each preset is a different screen.

[severin.menard]

But what is inside a <group> is not also inside a preset?