Alternate Inspector Property Organization Option

[Schadenvoid]

Problem:
While I generally find the Inspector's property orientation to be acceptable, the layout of exposed properties is somewhat awkward relative to the manner in which labels and properties are read in sequence.

Often you want to view all of a resource's properties to ensure that all settings are correct, but with Labels and Edits placed side-by-side, you're often forced to scan variables in a tiring, zig-zag manner.

Proposal:
Instead, it could be more fluid to have to option to view the Labels and Edits of all properties in a single column, with Edits placed on the next line down from their corresponding Labels. Like so:

Such an orientation would make it far quicker to assess the identity and setting of each of a resource's properties, especially in situations that require a wider inspector to allow for the viewing of properties with more information, such as significantly long strings.

[theraot]

I see value in the current organization. Although I also value horizontal space. So I wonder if this would be welcome as a setting.

Meanwhile, I think is all win for arrays, and a good compromise for dictionaries, as it would resolve this:

• Make dictionary key/value resources unfold full width in inspector if the other is not unfolded #11961

[Schadenvoid]

Yeah, I do too. Which is why I'd like it to just be an option, rather than a replacement standard.

I've had the same issue with dictionaries, for sure, so I agree.

[Sightwalker]

So I wonder if this would be welcome as a setting.

I second that. Having both options to choose (even if the current is the default one) would give quality of life to some people, like the ones that have eye conditions. And even to those that don't have any issues but care about where their eyes need to go this is a good solution.

[arkology]

Even games have the same layout as current. So, could you provide examples of purposed interface organization usage in other engines?

[Schadenvoid]

You're correct, I actually use the current layout type in my own game, however I feel like the difference is that I can much more greatly control the size and spacing of label and input elements so that they're comparatively large, close, and have enough space for the information they're displaying.

By comparison the inspector is far more interchangeable and varied in terms of the manner of data that can be displayed. Having the information aligned beneath the label allows each element to have the full breadth of the resource's inspector area with which to work, while the left-justification of edited elements would allow for the visibility advantages I explained in my initial post.

I also believe it to be a better solution than being able to resize the label half of the inspector area to be smaller, because then you are forced to deal with collapsing labels, should the player be allowed to adjust it beyond the largest label, or being limited by the size of the largest label should adjustment not be allowed past the largest label. Neither is particularly ideal, and my proposition carries neither detriment in exchange for the use of more vertical space, which tends to be a negligible issue since scrolling is trivial.

Exports are often grouped, as well, with enum and flag export options existing under a single label.

I can't say I've seen it before in another engine as Unity uses a similar layout, albeit with more space allocated to data rather than equal space for labels and data, but I feel like the benefits should be apparent from my explanation. It would also be fairly trivial to implement, since elements would just need to be arrayed in a singular column, rather than two columns that are (I imagine) separated by an even width H-Box.