It seems there is a bug in UMG’s combo boxes. Usually one can implement the “OnGenerateWidget” event in the combo box to populate the combo box’s options with custom widgets. This works fine when the widget that contains the combo box is being added directly to the viewport.
However, when that widget (which contains the combo box) is added as child to another widget, and that other widget is added to the viewport, then the “OnGenerateWidget” event function of the combo box is not being called any more.
Unfortunately this is a major bug in our project.
Any ideas, at least for a workaround?
Hello haimat,
I was unable to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.
Quick questions:
- Can you reproduce this issue in a clean project?
- If so, could you provide a detailed set of steps to reproduce this issue on our end?
- Could you provide screen shots of any blueprints that may be involved with this issue?
Hello haimat,
I am happy to hear that you have gotten things working again. I am going to mark your last post as the answer to this issue.
Make it a great day
Hey , thanks for your reply. I created a new project as requested, and that helped me to track down the reason for this issue. So the problem comes after creating a new binding function for the OnGenerateWidget event. I renamed that function afterwards, which led to issue as described. When I remove the binding and re-bind to that function (even if still renamed) it works again. Thanks!
1 Like