Consequences of making SPropertyEditorAsset public?

Development Pipeline & Plugins
, ,
1

SPropertyEditorAsset is the common interface for selecting/viewing UObject properties. I would like to make a custom layout for the property where I can change the sorting/display names of items in the asset picker. My expected workflow would be to create a IPropertyTypeCustomization for a particular UClass, instantiate a SPropertyEditorAsset widget, then modify the instance with new behavior or fields. However, SPropertyEditorAsset is private in UI and cannot be instantiated outside of core editor functionality.

Why are SPropertyEditorAsset and the other Property Editor widgets private, and what would be the consequences of moving them to a public folder in my local engine version?

[Attachment Removed]

2

Hi!

The intention here would be to use SObjectPropertyEntryBox in PropertyCustomizationHelpers, which wraps the SPropertyEditorAsset and passes along many of the properties. That said, I’m not sure *either* of these will give you a simple way to implement custom sorting or overriding the display names, so you might be looking at creating a custom picker anyway if you need that degree of control. Is there anything on SPropertyEditorAsset that would benefit from being piped through to SObjectPropertyEntryBox? If so, that might be a safer change than shortcutting directly to the underlying private widget.

Best,

Cody

[Attachment Removed]