Should Promote to Variable in a Functions Library not default to local?
This is pretty straightforward, as is the workaround, but I'm wondering if it's actually a bug or if I'm missing some purpose for this behavior.
If I drag off of a parameter inside of a functions library, such as a value in a break hit result, then select promote to variable, the functions library promotes it to a global variable, not a local variable. When I compile, I get the error message "The variable NewVar_0 cannot be declared in FunctionLibrary MovementFunctionsLibrary" which makes sense.
Now, it only takes an extra second to create a local variable and move on, but I'm curious why it defaults to this behavior, and doesn't offer promote to local variable on the action/context menu that drops down. Is this to favor the writing of functions inside of a blueprint rather than a functions library?
asked Jun 04 '19 at 10:25 PM in Bug Reports
Follow this question
Once you sign in you will be able to subscribe for any updates here