BindWidget, OptionalWidget and class mismatches
This seems like a dumb error, but I spent 20 mins wondering why today. I had another widget in my hierarchy named the wrong thing, and was getting a crash in C++ because of badly-initialized classes.
I would expect an error (or at least a warning) if the widget in my Blueprint does not match the expected BindWidget type.
asked Jul 03 '17 at 10:55 AM in Bug Reports
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.
answered Jul 10 '17 at 05:22 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here