- Create a new Actor class in the editor called PropertySpecifierActor:<\/li><\/ol>\n\n\n\n
![\"\"\/](\"http:\/\/blog.coolcoding.cn\/wp-content\/uploads\/2021\/01\/1181d0a4-74a1-4ab3-ac08-773bf590a75a.png\")
<\/figure>\n\n\n\n- Add the following property definitions to the class:<\/li><\/ol>\n\n\n\n
#pragma once
#include \"CoreMinimal.h\"
#include \"GameFramework\/Actor.h\"
#include \"PropertySpecifierActor.generated.h\"
UCLASS()
class CHAPTER_09_API APropertySpecifierActor : public AActor
{
GENERATED_BODY()
public:
\/\/ Sets default values for this actor's properties
APropertySpecifierActor();
protected:
\/\/ Called when the game starts or when spawned
virtual void BeginPlay() override;
public:
\/\/ Called every frame
virtual void Tick(float DeltaTime) override;
\/\/ Property Specifiers
UPROPERTY(EditDefaultsOnly)
bool EditDefaultsOnly;
UPROPERTY(EditInstanceOnly)
bool EditInstanceOnly;
UPROPERTY(EditAnywhere)
bool EditAnywhere;
UPROPERTY(VisibleDefaultsOnly)
bool VisibleDefaultsOnly;
UPROPERTY(VisibleInstanceOnly)
bool VisibleInstanceOnly;
UPROPERTY(VisibleAnywhere)
bool VisibleAnywhere;
};<\/pre>\n\n\n\n- Perform a Save, Compile your code, and launch the editor.<\/li>
- Create a new blueprint based on the class.<\/li>
- Open the blueprint and look at the Class Defaults section:<\/li><\/ol>\n\n\n\n
![\"\"\/](\"http:\/\/blog.coolcoding.cn\/wp-content\/uploads\/2021\/01\/04d585d0-842c-4de5-b9da-731758e27c2b.jpg\")
<\/figure>\n\n\n\n- Note which properties are editable and visible under the Property Specifier Actor section:<\/li><\/ol>\n\n\n\n
![\"\"\/](\"http:\/\/blog.coolcoding.cn\/wp-content\/uploads\/2021\/01\/1d639038-43e2-4ee8-abff-36f3ec2afa6b.png\")
<\/figure>\n\n\n\nLocation of the Property Specifier Actor<\/p>\n\n\n\n
- Place instances in the level and view their Details panels:<\/li><\/ol>\n\n\n\n
![\"\"\/](\"https:\/\/learning.oreilly.com\/library\/view\/unreal-engine-4x\/9781789809503\/assets\/16d4fe8b-9f98-40b7-96de-36f7d1188c15.png\")
<\/figure>\n\n\n\n- Note that a different set of properties is editable.<\/li><\/ol>\n\n\n\n
How it works…<\/h1>\n\n\n\n
When specifying UPROPERTY, we can indicate where we want that value to be available inside the Unreal editor.<\/p>\n\n\n\n
Visible* prefixes indicate that the value is viewable in the Details panel for the indicated object. The value won’t be editable, however.<\/p>\n\n\n\n
This doesn’t mean that the variable is a const qualifier; however, native code can change the value, for instance.<\/p>\n\n\n\n
Edit* prefixes indicate that the property can be altered within the Details panels inside the editor.<\/p>\n\n\n\n
InstanceOnly as a suffix indicates that the property will only be displayed in the Details panels for instances of your class that have been placed into the game. They won’t be visible in the Class Defaults section of the Blueprint editor, for example.<\/p>\n\n\n\n
DefaultsOnly is the inverse of InstanceOnly \u2013 UPROPERTY will only display in the Class Defaults section, and can’t be viewed on individual instances within the level.<\/p>\n\n\n\n
The suffix\u00a0Anywhere\u00a0is the combination of the two previous suffixes\u00a0\u2013\u00a0the\u00a0UPROPERTY\u00a0will be visible in all the\u00a0Details\u00a0panels that inspect either the object’s defaults or a particular instance in the level.As we mentioned previously, if you are interested in learning more about Property Specifiers, check out the following link:\u00a0https:\/\/docs.unrealengine.com\/en-us\/Programming\/UnrealArchitecture\/Reference\/Properties\/Specifiers<\/a>. <\/p>\n\n\n\n
See also<\/h1>\n\n\n\n
- This recipe makes the property in question visible in the inspector, but doesn’t allow the property to be referenced in the actual Blueprint Event Graph. See the following recipe for a description of how to make that possible.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
When developing with Unreal, it is common for programme […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27,1],"tags":[26],"_links":{"self":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts\/3045"}],"collection":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3045"}],"version-history":[{"count":1,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts\/3045\/revisions"}],"predecessor-version":[{"id":3063,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=\/wp\/v2\/posts\/3045\/revisions\/3063"}],"wp:attachment":[{"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3045"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3045"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.coolcoding.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- This recipe makes the property in question visible in the inspector, but doesn’t allow the property to be referenced in the actual Blueprint Event Graph. See the following recipe for a description of how to make that possible.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
- Note that a different set of properties is editable.<\/li><\/ol>\n\n\n\n
- Place instances in the level and view their Details panels:<\/li><\/ol>\n\n\n\n
- Note which properties are editable and visible under the Property Specifier Actor section:<\/li><\/ol>\n\n\n\n
- Add the following property definitions to the class:<\/li><\/ol>\n\n\n\n