How to make a button in one UMG invisible using another UMG?

Development Programming & Scripting UI
, , , ,
1

Hello

I am making a game using multiple widgets. My goal is to be able to have one “final” widget that has its buttons “unlocked” as the player clicks on the buttons on the other UMGs throughout the level. I’ve created all the widgets upon beginplay in my level bp so that I can freely reference them throughout. I use event dispatchers to set up what the buttons do in the level. Unfortunately, my goal is to have the player click on a specific button in order to make a button in a DIFFERENT widget become visible. I just don’t really know how to get a reference to the button in the level BP to make this happen. I know about the “set visible” node, I just don’t know how to access it from one BP to another, or even to make it happen in the level BP. I can’t get event dispatchers to reference other widgets as part of the original UMG functionality as I’m not making widgets inside of other widgets for design reasons. So I don’t know how to make these stupid buttons invisible when I click on the unlocking buttons. Any workarounds? Screenshots of node functionality would help immensely as I’m quite new to this.

2

There are many ways to work with references, consider the following:

Dedicate an actor as a central hub for widget communication. It can be a separate actor or you can use one of the existing classes, like GameMode for example - it’s easily accessible. When you create a widget, ensure you store the reference in your widget communication hub so you can always find the objects you need:

217332-widgetgamemode.png
217332-widgetgamemode.png932×770 141 KB

One thing I do not understand about your post:

I’ve created all the widgets upon
beginplay in my level bp so that I can
freely reference them throughout.

Since you are already working with Dispatchers (so you understand how registering works), which are somewhat more advanced than the direct communication I mentioned above, you should be able to push the information to the listening objects with ease.

Communicating with LevelBlueprint is best done via dispatchers, actually.