Developer Notes

This issue has been closed as 'Won't Fix' due to an extended period of time without updates. If this issue is important to you please let us know by posting on the AnswerHub or UDN, and Epic will re-open the ticket for further review.

Description

When a class uses the EditInlineNew specifier, the resulting class has some errors when interacting with the editor.

1. Unable to assign existing blueprints based off the class to an array of that class' type
2. Blueprints of that class' type not visible to the editor when selecting from a dropdown until they have been loaded manually

Note: This may only occur with classes added via a plugin, as in the test case.

Steps to Reproduce

1. Download the attached project
2. Generate project files and compile the project
3. Open the project
4. Create a new blueprint based off the KIRCBlueprintMessageHandler class
5. Select the Freenode actor in the level
6. Under "Message Handlers" in the details panel, select the drop down for Element 0 and try to select your new blueprint
Result: The array element remains unassigned
Expected: The array element should be assigned to this new blueprint
7. Save the project and close / reopen
8. Select the dropdown for the first element of the array as you did in step #6
Result: The new blueprint is not listed
Expected: The new blueprint should be visible in this list

To make the blueprint visible again: Open the new blueprint for editing and it will become visible in the dropdown from step #8.

Have Comments or More Details?

Head over to the existing Questions & Answers thread and let us know what's up.

1
Login to Vote

Won't Fix
ComponentTools
Affects Versions4.104.11
CreatedDec 10, 2015
ResolvedJan 30, 2017
UpdatedFeb 4, 2019