Describe the feature requested
Right now, action nodes will refresh (and therefore mark dirty the blueprint) if the action they point to is compiled. They should only do it when exposed properties change.
How does it help the user (you)?
Reduces the times a blueprint will be marked dirty and make sit easier to understand why.
[Optional] Propose an approach to the feature (the less we think the better!)
Use a custom blueprint generated class to keep track of whether or not properties changed during compilation.
Any other possible approach?
Use reflection to read the properties of the class and discover differences.
Describe the feature requested Right now, action nodes will refresh (and therefore mark dirty the blueprint) if the action they point to is compiled. They should only do it when exposed properties change.
How does it help the user (you)? Reduces the times a blueprint will be marked dirty and make sit easier to understand why.
[Optional] Propose an approach to the feature (the less we think the better!) Use a custom blueprint generated class to keep track of whether or not properties changed during compilation.
Any other possible approach? Use reflection to read the properties of the class and discover differences.