UI Text not updating on Front End

anonymous_user_6414cbc4 · October 14, 2020, 3:23pm

I have been having this issue with changing a widget’s text component. When running, the text updates from the default “BLANK” (

) to the required text that is read from the array passed into the ChangeOptionBoxes node (

). In the widget’s BP graph (

) I am setting the text and then printing it to the screen after it is set. When doing this the first time “BLANK” is replaced with the first options of the array and those options are also printed to the screen. On all other iterations of this function, the options are printed to the screen from the widget BP but the UI in game is not changing. Does anyone know what could be causing this or how to fix this issue?

This is screenshot of where ChangeOptionBoxes is called:

Screenshots: [1]: , [2]: , [3]:

Everynone · October 14, 2020, 3:57pm

I see your post fell victim to the AH formatting shenanigans.

What are the chances those text blocks have a variable bound to their fields?

anonymous_user_6414cbc4 · October 14, 2020, 4:08pm

Text blocks are not bound to anything. I had tried binding them to a get_text function but I had the same issue as above.

Everynone · October 14, 2020, 4:19pm

So what are you getting when you Print the Strings, not the text block data, just Strings you set? Are those correct?

anonymous_user_6414cbc4 · October 14, 2020, 4:24pm

Yes they print correctly.

Everynone · October 14, 2020, 4:41pm

So wait, the Option 1,2,3 Strings print fine but when you push the text in, it does not display in the text blocks? When you say the text blocks do not update - they remain / become empty or their text does not change.

Everynone · October 14, 2020, 4:42pm

Can you confirm you Print the actual strings BEFORE setting the text block.

anonymous_user_6414cbc4 · October 14, 2020, 4:55pm

Correct. They load the first text options but when setting them to the next options the text does not change and stays as the first options. And yes If I print the actual string before setting the text box those strings are correct.

Everynone · October 14, 2020, 4:58pm

And yes If I print the actual string
before setting the text box those
strings are correct.

In this case, the issue is not here - not in the screenshots you’re showing.

Something else is updating those blocks.

Everynone · October 14, 2020, 5:03pm

Can’t think of many interactions that could break this:

a variable bound to a block
something else updating the block on Tick
text block being updated again, with stale data
text block wrapped in some kind of invalidation panel

anonymous_user_6414cbc4 · October 14, 2020, 5:23pm

Thank you I’ll look into these possiblities.

Everynone · October 14, 2020, 5:50pm

Do tell how it goes.

Btw, on a somewhat unrelated note, if you wish to cut down on the blueprint spaghetti, consider the following when piping data into widgets:

You may have other reasons to set it up the way you do, though ofc.

anonymous_user_6414cbc4 · October 14, 2020, 7:50pm

Thanks that is cleaner. Sadly no luck so far. I have tried reworking the code and now have the options bound to something instead of calling an update text function. I am getting the same results of the backend printing the text correctly but it not actually being set for the UI. The binding appears somehow broken…

Everynone · October 14, 2020, 8:00pm

Update the widgets manually with literal text. Just push in some text and see if that updates them.

anonymous_user_850c0dd2 · December 5, 2022, 2:58am

Im also have such question,and have you resolve it now?