Why is this specific circular dependency breaking our blueprints?
This issue is fairly hard to explain, so let me know if I need to provide more information.
Also, once the "button" class is in this broken state, the engine crashes when we open the reference viewer on anything related to the blueprint.
We are currently getting away with other circular dependencies in our blueprints. Any ideas? Thanks!
asked Oct 27 '16 at 12:25 AM in Blueprint Scripting
The "button" class eventually references the playercharacter via some crazy chain of dependencies (just found this in the reference viewer)
It's going to be fairly hard to give you a straight answer based off of this alone.
The short answer is: clean up your blueprints not to have circular dependencies. Make use of "GetOwner" or "GetOwningController" for actors or widgets and then cast those to the appropriate player controllers if you want data from them.
If you need a widget to own another widget, make sure you give it an "Owning Widget" variable and set it up after a widget is spawned, that way you can use that owning widget reference as needed in a child widget.
The long answer would require a much better understanding of your project and how everything is set up, which I don't think will be time efficient if you have a lot going on inside of it.
answered Oct 27 '16 at 05:05 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here