Widget not generating OnKeyDown events

Development Programming & Scripting Blueprint
, , , ,
1

I have made a full-screen widget but can’t get the OnKeyDown events to fire. Here’s how I create it:

obraz
obraz1307×395 106 KB

The widget has “Is focusable” set to true.
What happens is that it fires in fullscreen as intended. However, I don’t get the event and when I press buttons I can hear my character move, jump in the background. And sure enough if I close the widget I can clearly see that the character was moving around. What am I doing wrong?

2

Sounds like the widget loses focus. Giving widget focus does not mean it cannot lose it again. They’re clumsy like that.

  • what are you passing as return value in onKeyDown?
  • do you actually want the character to move when the widget intercepts key presses?
3

In general I want only the UI to have the focus. Here’s my OnKeyDown:

obraz
obraz1549×308 122 KB

I guess you’re refering to using “Set Input Mode UI Only” instead of “Set Input Mode Game And UI” but I see no difference in using either. I can move my character in both cases.

4

Can you explain why you are removing the widget here? Or perhaps describe briefly what the general goal is? I’m assuming we’re dismissing a menu, right?

I guess you’re refering to using “Set Input Mode UI Only” instead of “Set Input Mode Game And UI” but I see no difference in using either. I can move my character in both cases.

I am confused. With UI Only, the player controller would be unable to process input - the inputs in the PC / Pawns / Actor would not work. But above you’re setting Game Only - this means giving the PC full control. Seems contradictory to what you’re attempting to achieve.

What are we actually doing?

Also,

image
image1435×379 105 KB

Think about the order of operations. If we’re in Game Only mode and try to give widget keyboard focus and only then change modes, it may not work. Perhaps give widget keyboard focus after changing from Game Only → Game and UI.

If I do this:

image
image1369×289 60.1 KB

image
image1386×386 102 KB

the isFocusable widget will happily Handle and hungrily Consume any and all keyboard input.

If I click outside the widget area, the widget will lose focus, which is fine.

2 Likes
5

I’m showing the widget when you get into a trigger. Then I want it to close when you press space and do nothing if you input anything else. It’s a fullscreen widget so I don’t want the character to move.

I’m destroying the widget in OnKeyDown when you press space as I want to close it then. Should I implement it in a different way?

The setting of Input to GameOnly inside OnKeyDown is to restore input to PC after the widget closes.

I’ll try changing the order of keyboard focus!

EDIT:
for the example you provided - I also tried this. Print is not called and if I set breakpoint on it, it never gets called.

6

I’m destroying the widget in OnKeyDown when you press space as I want to close it then. Should I implement it in a different way?

I’d change the order, Remove after switching to Game Only. Probably irrelevant here but safer in the long run.

A bit odd, that’s the default behaviour. Wondering what else is going then. Can you explain how the very first pic is triggered? What fires that logic?

I’m showing the widget when you get into a trigger.

Can we see that? What are the chances more than 1 widget is created?

7

Changing the order of focus to be after setting input mode seems to have fixed the issue. Thank you!

1 Like