# Tooltip widget strange behavior on creation (not updating part of the information)

**URL:** <https://forums.unrealengine.com/t/tooltip-widget-strange-behavior-on-creation-not-updating-part-of-the-information/2261262>\
**Category:** UI\
**Tags:** unreal-engine, question\
**Created:** [January 5, 2025, 6:30pm UTC](https://forums.unrealengine.com/t/tooltip-widget-strange-behavior-on-creation-not-updating-part-of-the-information/2261262 "2025-01-05T18:30:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hdslayer1990](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hdslayer1990/32/1041576_2.png) [@hdslayer1990](https://forums.unrealengine.com/u/hdslayer1990)\
**Post date:** [January 5, 2025, 6:30pm UTC](https://forums.unrealengine.com/t/tooltip-widget-strange-behavior-on-creation-not-updating-part-of-the-information/2261262/1 "2025-01-05T18:30:46Z")

</div>

I have a custom widget designed as a card to use as a tooltip. The issue comes to this:  
I create the widget and fill all the exposed variables. The widget is created and shows the correct information for each element it’s supposed to show. One of the requirements is to use an event dispatcher on the parent blueprint, that get’s called when the user selects a color theme for the entire UMG.  
Everything else is working, and changes the color scheme (kinda automated, kinda brute hard coded), Used the same logic on the tooltip widget and it gets the event dispatch, and in debug (thanks to the Almighty PrintString) it shows the correct value for the variable, but the actions it must perform are not updated.  
Here’s an overview of the setup:  
Binding the dispatcher that exists on the parent BP class, and uses the Theme variable heredated from the parent. I did not declared the variable in this BP, nor the Event dispatcher. I’m using the same logic everywhere and it works.

 ![Captura de pantalla 2025-01-05 210227](https://d3kjluh73b9h9o.cloudfront.net/original/4X/7/2/c/72c709bd4ac2eae413aea48ed4a5fc311cc1f588.png)  
I call the initialization of the color theme both on construction and on event dispatch.  
Inside, i do some nearthdenthal logic to update the elements i need changing colors. It works everywhere else.  
 ![Captura de pantalla 2025-01-05 210710](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/c/a/acaab7c2a442085eaa267e92c95bf21728ac9b58.png)

Let’s now run and see the results.  
I initialize in a given theme.

 ![Captura de pantalla 2025-01-05 211012](https://d3kjluh73b9h9o.cloudfront.net/original/4X/1/3/0/13064173cabd9e4689b102d2f86fe4dd5f0253f2.png)

And the tooltip widget looks like this:

 ![Captura de pantalla 2025-01-05 211029](https://d3kjluh73b9h9o.cloudfront.net/original/4X/f/6/1/f61fc449c3856aff07dac39837bd59242dd4341f.png)

and on creation of each one i get the color scheme on debug  
 ![Captura de pantalla 2025-01-05 211059](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/9/2/a92ad8ac155e848327d7b493942271b728f76486.png)

Then i switch to the other scheme:

 ![Captura de pantalla 2025-01-05 211142](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/3/d/63d4d6f0e5e71e91bec9393bef59f19d4229bc83.png)  
and immediately adter switching i get this on the screen, even tho i only have the print string on the tooltip widget  
 ![Captura de pantalla 2025-01-05 211117](https://d3kjluh73b9h9o.cloudfront.net/original/4X/8/d/6/8d6a3a8c46d03ded72d1658c8a9e74dfb5b9cc82.png)  
there’s two conclusions i make from this: the dispatcher works, and it seems like they are not beign destroyed, but collapsed and they are still somewhere, right? because the more ojects i hoover and get the tooltip, the more logs i get when i chage the theme in the settings.  
Now, the logic for the widget creation is this:  
 ![Captura de pantalla 2025-01-05 211918](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/a/2/aa2ba7b3f92711d275fb2d1f942939bb951fbe65.png)  
some text formating, blah, blah, blah… and the theme variable is passed from the parent widget (that is a few levels above, aka. main hud, and it’s the only declaration anywhere). And to manage the staying in memory issue, i tried this:  
 ![Captura de pantalla 2025-01-05 212604](https://d3kjluh73b9h9o.cloudfront.net/original/4X/b/d/b/bdb80a8564e1b5e371fdbb75bb39109ef964548d.png)  
some validity check on the storage variable, and if it already exists, remove from parent (aka. try to destroy, without calling garbage collection XD )  
 ![Captura de pantalla 2025-01-05 212615](https://d3kjluh73b9h9o.cloudfront.net/original/4X/c/0/2/c02f2f298afa0d9ce71d6fcc91d5ce03e1ba8682.png)  
and storing it at the end of creation.  
So far, i keep getting the same results. They still get created on the first theme i lauch the game on, and won’t update, and i still get the same degug log of many existing tooltip widgets but not visible when in change color theme.

---

<div class="post-metadata">

**Author:** ![Everynone](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/everynone/32/1135017_2.png) [@Everynone](https://forums.unrealengine.com/u/Everynone)\
**Post date:** [January 8, 2025, 4:58pm UTC](https://forums.unrealengine.com/t/tooltip-widget-strange-behavior-on-creation-not-updating-part-of-the-information/2261262/2 "2025-01-08T16:58:05Z")

</div>

One thing that immediately jumps out is referencing the Hint Card which should be, generally, unnecessary. The tooltip system releases widgets on its own without the need for manual removal. And since it does get referenced manually here, perhaps the Garbage Collection is unable to scoop it up and things become jumbled a wee bit.

Have you you tried it without the extra variable?

---

<div class="post-metadata">

**Author:** ![hdslayer1990](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hdslayer1990/32/1041576_2.png) [@hdslayer1990](https://forums.unrealengine.com/u/hdslayer1990)\
**Post date:** [January 9, 2025, 10:15pm UTC](https://forums.unrealengine.com/t/tooltip-widget-strange-behavior-on-creation-not-updating-part-of-the-information/2261262/3 "2025-01-09T22:15:49Z")

</div>

Yes, I promoted it to try to destroy it manually because of the behavior I explained. And about the Theme variable not updating, I just called the same widget from another blueprint, and from there it does update. Both caller blueprints have the same hierarchy, actually, the second one is a modified duplicate of the first one, and I pass the same parameters on the same events (inherited) to create the tooltips. I still have the debug output of them being in memory, but I don’t care (for now) as long as they update the Theme, but the first one still doesn’t.
