input management

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

radubolovan

Hello, I have a screen (scn) that has a script which handles the input as follows:

func handle_input(): &nbsp; &nbsp; print(&quot;action accept&quot;) func input(event): &nbsp; &nbsp; if(event.is_action_released(&quot;ui_accept&quot;)): &nbsp; &nbsp; &nbsp; &nbsp; handle_input() 

Also, the scene has a Control object as a child. This Control object has also a button as a child. And this button is attached to a function in the control's script as follows:

func _on_button_released(): print(&quot;button pressed&quot;)

When I press the button, the visual effect of the button is OK, but the function "on_button_released()" never gets called. As far as I can see the function "input" from the scene's script "eat" the input. My question is: how to pass the input event to children nodes? Is it possible to pass the input event to children as something like the following?

func _input(event): &nbsp; &nbsp; my_child.handle_inlupt(event)

    

Akien

You should likely use the [tt]pressed[/tt] signal instead of [tt]released[/tt], see https://github.com/godotengine/godot/issues/4625 (I agree it's a bit confusing).Input events are passed to children nodes automatically unless the parent node marks them as handled. See http://docs.godotengine.org/en/latest/tutorials/engine/inputevent.htmlIf need be, you can of course pass an event to a custom function of the child node with [tt]my_child.handle_input(event)[/tt], provided you declared the function in the child node's script with a parameter ([tt]func handle_input(event):[/tt], which you did not do in your example).

radubolovan

Thanks a lot for your reply and for the help.Using pressed against the released signal works fine indeed.About "handle_input" function that I suggested, I didn't mean just to call a function. I thought that was a function that automatically resolved the issue that I had. I didn't thought that was a bug about signaling the "released", I thought that was an issue abut "someone" (as an object) was killing the input and not passing it into the child so I thought that I might passing it myself.Do you have any idea if the "released" signal will be fixed soon?On mobile phones this is not a problem, but when releasing the game/app on a computer (Linux/MacOS/Windows) this could become an issue when using a mouse and following a desing document.