Widget fails to load but only when Editor opens.

Hello.

Let´s see if somebody can help me here, please check screenshots.

Step 1.

116397-exception+1.jpg

The blank square, is an inventory, is the same class as BELT, but with rows and columns. So BELT and INVENTORY are 2 instances of the same class, since a few days ago, this started happening, like it was broken.

Step 2.
I will erase this instance, and re-create it, with the same name and everything…
So you can see it here working, without changing anything…

116398-exception+2.jpg

Step 3, test if the game works… and in fact! it works ok, no exceptions or warnings at all.

116399-exception+3.jpg

Step 4.
Save all, close everything, close unreal editor.
Re open game solution, and what I can see, is that the problem shown in step 1, happens again, and I don´t know what else to test, or to debug, everything looks ok!!!

Can someone point me what could be failing here? and why an instance of the same class fails and the other works ok?

116400-exception+4.jpg

Thanks & regards.
Leonardo.

I think I found out a lead of the problem, this started happening when I changed the way that I retrieve Image of the Button, when working it was done by binding a variable, and now it’s binded by a method that retrieves the variable.

The thing is, my method has a IsValid, and returns an empty SlateBrush in case of not valid, so… why this is breaking up the game? and why is breaking up only when opening application???

strange…

Hello leofucci,

I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  3. Could you provide screen shots of any blueprints/widgets/settings that may be involved with this issue?
  4. Could you make sure that you do not have any circular dependencies for the widgets being used?

Hello leofucci,

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.

Thanks,