Description

When looking at the details of a UObject contained in a Data Asset, some categories are shown even though they should not be. If a category is marked as hidden in the parent class, it will be shown in the Data Asset (though variables in that category will not be shown). In addition, if a UFUNCTION from the Blueprint's parent class has been overridden in the Blueprint, another empty category named "Event Graph" will be shown in the Details panel.

REGRESSION:
Yes. In 4.20.3, hidden categories and the "Event Graph" category are not shown in the Details panel.

Steps to Reproduce
  1. Download the attached project (project created in Main at CL 4555827).
  2. Associate the project with your version of Main.
  3. Build the project in Visual Studio.
  4. Open the project in the Editor.
  5. Create a new Blueprint that derives from the MyObject class.
  6. Create a new Integer variable in the Blueprint. Leave the variable's category set to Default.
  7. Create a new Bool variable. Set the variable's category to "DoNotShow" (this is a hidden category in the MyObject class).
  8. Override the Receive Event Triggered function.
  9. Compile, save, and close the Blueprint.
  10. Create and open a new Data Asset that derives from MyDataAsset.
  11. Add an element to the InstancedUObjects array.
  12. Set the new element to the Blueprint created in step 5.
  13. Expand all of the categories in the details for the first element of the InstancedUObjects array.

RESULT:
The "Do Not Show" category is shown (but the variable in the category is not), and there is another category present named Event Graph.

EXPECTED:
Only the Default category is shown since the other categories are empty (as far as the Details panel is concerned).

Have Comments or More Details?

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

3
Login to Vote

Fixed
ComponentTools
Affects Versions4.214.22
Target Fix4.22
Fix Commit4569788
Main Commit4676940
Release Commit4862694
CreatedNov 12, 2018
ResolvedNov 19, 2018
UpdatedFeb 12, 2019
View Jira Issue