You've already forked UnrealEngineUWP
mirror of
https://github.com/izzy2lost/UnrealEngineUWP.git
synced 2026-03-26 18:15:20 -07:00
[SmartObject] access to activity tags should go through SmartObjectSlotView
+ Tags Filtering Policy now only affect TagQueries from the definitions and applied to UserTags provided by requests + Tags Merging Policy added for Activity Tags #rnx #rb josselin.francois #preflight 621fab91257fd6e0996de3b2 #ROBOMERGE-AUTHOR: yoan.stamant #ROBOMERGE-SOURCE: CL 19225863 via CL 19236663 via CL 19236832 via CL 19236900 #ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v921-19075845) [CL 19237559 by yoan stamant in ue5-main branch]
This commit is contained in:
+14
@@ -245,6 +245,20 @@ public:
|
||||
return *(EntityView.GetConstSharedFragmentData<FSmartObjectSlotDefinitionFragment>().SlotDefinition);
|
||||
}
|
||||
|
||||
/**
|
||||
* Fills the provided GameplayTagContainer with the activity tags associated to the slot according to the tag filtering policy.
|
||||
* Method will fail a check if called on an invalid SlotView.
|
||||
*/
|
||||
void GetActivityTags(FGameplayTagContainer& OutActivityTags) const
|
||||
{
|
||||
checkf(EntityView.IsSet(), TEXT("Definition can only be accessed through a valid SlotView"));
|
||||
const FSmartObjectSlotDefinitionFragment& DefinitionFragment = EntityView.GetConstSharedFragmentData<FSmartObjectSlotDefinitionFragment>();
|
||||
checkf(DefinitionFragment.SmartObjectDefinition != nullptr, TEXT("SmartObjectDefinition should always be valid in a valid SlotView"));
|
||||
checkf(DefinitionFragment.SlotDefinition != nullptr, TEXT("SlotDefinition should always be valid in a valid SlotView"));
|
||||
|
||||
DefinitionFragment.SmartObjectDefinition->GetSlotActivityTags(*DefinitionFragment.SlotDefinition, OutActivityTags);
|
||||
}
|
||||
|
||||
/**
|
||||
* Returns a reference to the definition data of the specified type from the main slot definition.
|
||||
* Method will fail a check if the slot definition doesn't contain the given type.
|
||||
|
||||
Reference in New Issue
Block a user