Add option to reverse (or customize) node order in Inspector

[recursivenomad]

Describe the project you are working on

Misc. XR experiences

Describe the problem or limitation you are having in your project

When I wish to edit or view the same common property across multiple different node types (such as transforms), it becomes very fatiguing having to hunt for the property at varying heights in the inspector.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

If the properties in inspector could be optionally ordered from most generic to least generic (or, follow a custom ordering hierarchy defined in a list), then that would show the same common components at the top of the list, allowing the user to much more clearly understand and compare common properties (such as transforms).

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

Before	After
Camera3D	Node
Node3D	Node3D
Node	Camera3D

If this enhancement will not be used often, can it be worked around with a few lines of script?

I do not know, I am not familiar with editor scripting at this time.

Is there a reason why this should be core and not an add-on in the asset library?

It seems like a basic editor preference to me, as it was already discussed as being included if there were enough support for it here.

[AThousandShips]

If the properties in inspector could be optionally ordered from most generic to least generic (or, follow a custom ordering hierarchy defined in a list), then that would show the same common components at the top of the list, allowing the user to much more clearly understand and compare common properties (such as transforms).

That's a very subjective assumption, I'd say the opposite is true and that the order as it is right now conveys the common properties, and that's probably the reason why this order was picked in the first place

But this could absolutely be configurable, with the current order being the default

Also the most common properties are usually the least modified which means putting the least common one at the top helps access the properties users are most likely to be modifying a lot of the time

[recursivenomad]

Yes, it is subjective! Which is why I would value this as an option, not a default change 🙂

While I agree that the current order accurately communicates the hierarchy of property inheritence & specificity, and the current top of the list will be more likely to be interacted with, I find it does not lend itself to easy parsing of information for how my workflow flows. I agree it should not be the default, but I value consistent readability over most-likely/common property access, and an option to customize this order to reflect that preference would be welcomed for my preferences.

[Meorge]

As something of a workaround, note that you can mark properties as "favorites" and have them pinned to the top of the inspector view for easy access. To do this, right-click the property label, then click "Favorite Property" from the context menu.