3D Widget combo box not dropping down

Hi

Just a quick one.

TL;DR

3D Widget Combobox is interact-able, but when clicking on it to drop list down, it does not drop down.
Combobox works perfectly ok when added to viewport however.


Recreation steps:

1. Create widget blueprint with a combo-box in it, with several entries. Also change tint on hover and clicked.

2. Create a blueprint actor.

3. Add widget component to blueprint actor.

4. Add stuff to event graph to allow player to switch control to UI and Game.

5. Hover mouse over combobox and combobox will change tint to the colour chosen in step 1.

6. Click on combobox and it will change tint to colour chosen in step 1.
However the combobox will not drop down

Add widget to viewport however, and the combo box behaves perfectly normal.


I have a computer screen which players can interact with while in game, running around.
On this computer screen, I would like to allow players to choose an option from a drop down menu, and once that option is chosen, it will do an action.

The problem is, while I can interact with my computer blueprint, I can enter information into text fields, I can click buttons, navigate menu’s and so on, so forth, however when I click the combobox to make it drop down, it does not drop down. (IF it is a widget within a blueprint. It works in my UI in my options screen etc).

To make sure that the combo box was recognizing my mouse input, I changed the hover tint and click tint, and set pivot to 0,0 rather than 0.5, 0.5, and it recognizes my mouse input when I hover, and when I click, but it just won’t drop down and show me any of the options.
Also, I added 5 default options, I set the selected option. I also added another 5 options on the “Construct” event within the widget.

I wasn’t sure if I should submit this as a bug report or not at first, I thought maybe it was user error, but pretty certain it’s not. I’d be kind of happy if it was just user error though, that means I could fix it right away :stuck_out_tongue:

Hello Otreum,

After doing a bit of digging I have found that this issue caused by a known issue (UE-20777) and that it has been reported to the developers for further consideration. I will be sure to bump up the community interest for this issue. Thank you for your time and information.

Make it a great day

Thank you Rudy, that was a super duper quick response!