Differences

This shows you the differences between two versions of the page.

--- en:toolworks:docs:apparatus:trait [2021/06/18 22:53] – vladius
+++ en:toolworks:docs:apparatus:trait [2022/06/07 10:53] (current) – Fix structure name. jispar
@@ Line 5: / Line 5: @@
 ===== Changing Traits =====
-The Trait data is what called value-type in some languages. The behavior is somewhat native for UE environment. This basically means that in order to change a Trait's data you have to read it, change it and then write it back, re-apply it to the Subject.
+The Trait data is what called value-type in some languages. The behavior is somewhat native for UE environment. This basically means that in order to change a Trait's data you have to read it, change it afterwards and finally write it back re-applying it to the Subject. This procedure is necessary to guarantee the atomic and secure nature of the Trait types. Don't be too much scared by this copying routine since the procedure has some very high chances of being cache-local.
 ===== Garbage Collection Notes =====
@@ Line 23: / Line 23: @@
 You should mainly refer to the official Unreal Engine manual on creating [[ue>ProgrammingAndScripting/GameplayArchitecture/Structs/UsingStructs|UStructs]].
-You basically create a header (.h) file and optionally a source (.cpp) file. An example of such header-only Trait would be:<code cpp>
+You basically create a header (''.h'') file and optionally a source (''.cpp'') file. An example of such header-only Trait would be:<code cpp>
-// Fill out your copyright notice in the Description page of Project Settings.
 #pragma once
 #include "CoreMinimal.h"
-#include "MyTrait.generated.h"
+#include "Moving.generated.h"
 /**
- *
+ * The state of being moved with a certain velocity.
  */
 USTRUCT(BlueprintType)
-struct MY_API FMyTrait
+struct MY_API FMoving
 {
 	GENERATED_BODY()
@@ Line 50: / Line 48: @@
 You could omit the [[ue>ProgrammingAndScripting/GameplayArchitecture/Properties|UPROPERTY]] specifications but
-with the fields exposed like that you can now use ''MyTrait'' both in your C++ code and within BPs.
+with the fields exposed like that you can now use ''FMoving'' both in your C++ code and within BPs.
+==== Blueprint Workflow ====
+As basically every Unreal Engine's ''USTRUCT'' is actually a Trait creating one through the Editor is quite simple. Rigth-Click on some empty space inside the Content Browser and choose **Blueprints** → **Structure**.
+{{ :en:toolworks:docs:apparatus:ue-create-bp-struct.png?nolink |}}
+This will create a new asset file right inside the designated folder. You should give it an appropriate name after that.
+{{ :en:toolworks:docs:apparatus:ue-name-bp-struct.png?nolink |}}
+That's basically it and from now on the created structure can be used right inside your [[en:toolworks:docs:apparatus:filter|Filters]].