Description

Essentially, A bug in --[Link Removed]-- comes up with only customized struct property.
If a struct doesn't have customization, it can be displayed compact without "Element X" node hierarchy.
It is the same as UE4.23 behavior.
I write a code for it.

bool FDetailPropertyRow::NeedsKeyNode(TSharedRef<FPropertyNode> InPropertyNode, TSharedRef<FDetailCategoryImpl> InParentCategory)
{
	UStructProperty* KeyStructProp = Cast<UStructProperty>(InPropertyNode->GetPropertyKeyNode()->GetProperty());
	UStructProperty* ValueStructProp = Cast<UStructProperty>(InPropertyNode->GetProperty());
	return KeyStructProp != nullptr || GetPropertyCustomization(InPropertyNode->GetPropertyKeyNode().ToSharedRef(), InParentCategory).IsValid() ||
		( ValueStructProp != nullptr && GetPropertyCustomization(InPropertyNode, InParentCategory).IsValid() );
}

 

Before

  [Image Removed]

 

After

  [Image Removed]

 

Steps to Reproduce
  1. Create Blueprint
  2. Add Integer variable
  3. Change the variable to a Map
  4. Set the Value type to BoxShpereBounds
  5. Compile
  6. open Class Defaults pane
  7. Add an element to the variable

RESULT

Map which has structure type value always places inside "Element X" node.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-87321 in the post.

1
Login to Vote

Won't Fix
ComponentUE - Editor - UI Systems - Slate
Affects Versions4.24
CreatedJan 23, 2020
ResolvedJul 19, 2022
UpdatedJul 19, 2022
View Jira Issue