Custom Verse UI Buttons Mess Up Layout When Pressed

Development Programming & Scripting
, ,
1

When making a custom button using the button class I consistently notice what looks like extra padding being added around the button whenever it’s pressed down/clicked.

I’ve seen islands that seem to use custom buttons and do not have this issue, but everything I’ve tried results in this issue.

Does anyone know what’s going on?

Here are some screenshots:

No button pressed (Lay out looks as intended)

image
image893×581 129 KB

Buy button pressed (Significant padding added to sides of Buy button, stretching the entire menu horizontally)

image
image870×491 107 KB

Close button pressed (padding added to bottom of menu, stretching it slightly vertically)

image
image806×393 86.9 KB

The code looks like this

Simple User Widget with an Overlay as the topmost element

ButtonWidget:WB_Button := WB_Button{}

Custom button using button class

Button := button:

        Slot := button_slot:

            Widget := ButtonWidget

            HorizontalAlignment := horizontal_alignment.Fill

            VerticalAlignment := vertical_alignment.Fill
2

I was able to ask this question during this livestream and Derek Diaz was kind enough to answer! This issue is something they’re very much aware of and will be addressed soon - not the very next release but soon after.

The livestream was wonderful and is definitely worth the watch if you’re interested in pushing the envelope of UI in UEFN. Thanks again!

3

I want to know how stuff like this passes basic QA. These days it’s less of a case of what new features does an ecosystem update add, and more of a case of what obvious thing has it broken. Now we have to spend hours trying to find out if it’s a problem with our code or something Epic broke in an update, and when it’s invariably something that’s been broken, which hoops do we need to jump through to return to past functionality.

There hasn’t been a single update in the past six months (at least) that hasn’t either broken a working feature or shipped a new feature that was obviously never tested because the suggested use case breaks it.

I’m willing to bet all feature testing is done on a version unavailable to us so they don’t see the issues we do, otherwise I don’t even know what.