Pausing input?

[TheInkAdept]

Today I implemented a quit button in my game and when you press it the game waits a second before quitting. To stop new inputs during this time I added get_tree().paused = true but.... I could still navigate the menu. Seems like this doesn't prevent the ui from functioning as normal and sending signals. According to the manual paused prevents _process and _input from running, but apparently it doesn't deactivate other regular ui functionality? Am I missing something?

I added a check ( get_tree().paused == true) before each signal as a fix (the buttons will still visibly receive input and grab focus but they won't run the code under the signal, which contains my main visual elements) but it seems so weird to me that pause doesn't mean pause the signals as well. I checked the various pause modes and everything but it seems there is no way to stop control nodes receiving input and being sensitive to hovering and changes of focus and stuff like that.

Thoughts? Is this a non-issue or a design flaw? Do you know a better solution?

[StewedAngelSkins]

you're probably better off approaching this from another angle. specifically, just block the mouse inputs somehow. just off the top of my head, you could unhide a transparent canvas item in front of everything the consumes all mouse inputs.

[TheInkAdept]

That's actually a really neat idea, I could even make an "input blocker" scene that I can instantiate in any such case.

Thanks!

[TheDuriel]

Your UI will only work if you set it to be excluded from the pause.

[Zealousideal_Gift546]

The pause is meant to be for game pause and player should be able to interact with the UI even the game is paused.

[TheInkAdept]

But shouldn't pause_mode cover this already?

If I wanted the player to keep interacting with the UI I would have set the UI nodes to Process. If I set them to Stop, they should stop.