Hi, people.
I was wondering if you know any way of avoid using Header files to define static template methods (bc linker gets confused with symbols when you put the definition on Source file, like shows the following capture)
First, you cannot expose templates to blueprint. At least not easily. It is possible to write generic functions for specific containers that are supported by blueprint.
Second, generally template definitions (the body of the function) have to be visible to any place that uses it so it has to go into the header (unless it’s a template only used within one cpp).
Now, in your particular case you could declare a function like this:
The ‘Type’ parameter will create a drop down that allows you to select a component type and the metadata markup will autocast the return value to that type.
BUT: You shouldn’t need to write your own library function for this. Actor already has a template function that you can call like this: Actor->GetComponentByClass< CompType >( ) that does exactly what you want (sans logging).
Also, there is already a blueprint node to do this that works the way you want where you pick a type and the return is autocast for you.
Thank u, @MagForceSeven.
I am not that much interested on expose this method to BP, I just did it for possible future testing on BP; anyway, I noted your valuable information for the next time.
I already knew templates must be on header, but I was looking for some kinda trick to bypass this necessity and be able to define it on source. I guess I have to get over it my order obsession in this case .
I thank you too for the tip about direct get method with already casted component, but I tried it and I think you maybe meant to FindComponentByClass<CompType>().
.