why is interaction: receive hardware input disabled when placing a widget in an actor blueprint

Widgets in focus receive input from pointing devices / keyboard (keyboard focusable is yet another story altogether, though). Widgets that are not in focus do not.

because it is active and most active (priority) and perhaps full screen?

Perhaps.

can you block a single widget from having focus?

  • set the widget root element to:

To clarify: any widget can be made non-interactive, but if you do it at root level, all widgets will inherit the behaviour.

  • or disable collision on the widget component in world space:

  • or:

If you want to avoid general focusability. However, if you’re using native buttons, it will probably not work too well. Buttons are, somewhat, focus hungry to say the least…


Also, widgets receive notifies:

We can redirect focus where it’s (not) needed.

1 Like