This also brings up a good point about how `FName::NameToDisplayString` works. Currently it will only remove a 'b' character if a boolean is given, which leads to inconsistent results throughout the editor.
Many people want to follow a "m_Variable" naming scheme, which should also be automatically cut out for native variables in blueprints. Currently if you use a "m_" naming scheme you will not get a cleaned up version of the display name, and have blueprint nodes with incorrect "M Variable" names.
[Image Removed]
UPROPERTY(BlueprintReadWrite, EditAnywhere, meta = (DisplayName = "Internal Property Dis. Name")) int32 m_InternalProperty; UPROPERTY(BlueprintReadWrite, EditAnywhere, meta = (DisplayName = "Internal Mesh Dis. Name")) UStaticMeshComponent* m_InternalStaticMeshProp;
Result: The variable is displayed as "m_InternalProperty"
Expected: The variable is displayed as "Internal Property Dis. Name"
How does TextureRenderTarget2D get TArray<uint8> type data?
How to delete some elements correctly when deleting an array loop?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
Why does the REMOVE method of map container remove elements have memory leaks?
How do I set a material as a post-processing material?
What is the difference between Camera and CineCamera?
How to assign a value to a member of UMG's UMaterialInterface pointer type in C++?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-103069 in the post.
2 |
Component | UE - Gameplay - Blueprint Editor |
---|---|
Affects Versions | 4.26, 5.0 |
Target Fix | 5.0 |
Created | Nov 12, 2020 |
---|---|
Resolved | Jan 6, 2021 |
Updated | Nov 30, 2022 |
7572 - projectgheist |