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

Without knowing the exact scenario, it’s impossible to suggest something directly.

  • if you have a widget component with a native button that loves to steal focus, you can get back to the viewport immediately like so:

Again, no clue what is the actual scenario we’re dealing with.

i follow the thing principled

This is, sadly, too vague of an answer. Does it mean you do precisely what the bullet points outlined?


if you’re not sure about the technicalities, describe it from the end user’s perspective. What are we doing / what is happening?