I’ve found similar answers on here, but not specifically what I’m looking for. I’ve created a start menu that has several transparent buttons. I’ve set the z-order of the backgorund image to cover the whole screen, which works fine. I assume there is a way to do the same with the buttons (so they are a higher z-order than the button text). But I can’t find how to do this anywhere. Any advice. I’m guessing it’s something really simple that I’m missing!
Children of Overlays respect hierarchy order, and Children of Canvas follow explicit zOrder. See here:
I tried playing around with the
hierarchy based on that, but it either
puts the button above/under the button
text or moves it to the end of the
vertical box where the buttons are all
located.
There’s a misunderstanding here. I’m talking about panels that control the zOrder - Overlay children follow hierarchy order, and Canvas dictates zOrder by Index - as seen in the attached link.
I basically want to be able to click
on anywhere within the button,
including the area where the text is,
and the new screen will open up that
the button triggers.
Text goes into the button and you set its desired visibility. Although the latter is optional due to the nature of buttons and the way they hungrily consume input.
And if you do not want the text contained within the button, use an Overlay and / or Canvas as a parent for both - this gives you the ultimate freedom of offsetting.
Each and every element in UMG comes with Visibility - granular control over what shows and can interact with player’s input.
I tried playing around with the hierarchy based on that, but it either puts the button above/under the button text or moves it to the end of the vertical box where the buttons are all located.
I basically want to be able to click on anywhere within the button, including the area where the text is, and the new screen will open up that the button triggers. But clicking on the button text just brings up the cursor bar even though it’s in the middle of the button. Maybe I’m taking the wrong approach entirely. I assumed it was because the button was behind the button label, but now I’m not sure.
I found the answer. It was something totally random in the end. Tooltip was enabled in the behaviour bit. Once I turned that off, it removed the line and let me click on the text as part of the button trigger! But thank you for the advice above, as that will likely be useful at some other point in development. Cheers!