0 votes

Hi

Is there a way to filter mouse events?

I have a simple scene which has a Node2d (Root), with a sprite (Background) and camera2d (Camera) as children. The sprite is an image which is bigger than the viewport. I have a attached a script to the Node2d which is overriding _input(event)

When I drag around the scene (by handling InputEventScreenDrag) i move the camera so you can "look" around the entire background sprite. This works fine.

The issue I'm trying to resolve is that a whole lot of other input events fire (mousebutton, screentouch, etc) as well (obviously), but since they all come into the _input function separately how do i filter them?

For instance if a drag has happened, I don't want this also to be seen as a tap (screentouch) as eventually i want this to do something else.

Also if I have add other child sprites to the root Node2d and "screentouch" one of those, how do I stop the events from firing on its siblings or parent as well?

I've just started playing with godot and gone through a lot of tutorials, but these mostly focus on keyboard entry. If I need to change the hierachy or the tree, or use different objects, or if its a code solution, any pointers, references, etc would be great.

Thanks.

asked Sep 3, 2018 in Engine by tyronewatt (12 points)

How do You check for mouse input type?
Because maybe all you need is some if/elif/else structure to filter the events...

Thanks, but that doesnt work, the events come through as and when they happen, so the _input(event) function is called multiple times with a single event milliseconds apart, depending on how long you hold the buttons down for.

So if/else can redirect the event to a particular function, but you really need to know what the previous event(s) were that was passed to the function.
Since mousemove is also an event then _input(event) could be called 100's of times between the mousedown and mouseup event, and then you would have to determine whether a drag event happened between those events to determine whether or not it was a click event. Since a mousedown and touch pressed and mouseup and touch released both fire on on a single click event, you cant handle both as you would essentially get two virtual clicks for every one physical click, so you would need to combine those events into a single event.

All of the above is programatically possible, but it seems like a lot of low level work, for a higher level tool. I was hoping that someone who knows godot better, would be able to point to some classes or implementation method, or node type, that was already built in that I've missed in the docs.

That I do not know yet - I am a beginner also :)

1 Answer

+1 vote

When you use input callbacks, filtering event is done with ifs, like this:

if event is InputEventScreenDrag:
    # Do your drag

And you will always get only the drag event inside that if block. This is just how events work, at least when using _input.
If you did not use an if then you maybe got lucky because many events share the same properties, and you could have had errors by trying to access inexistent ones depending on which type of event the function received.

If you want nodes to interrupt events, I think you should not go with only _input because that one happens always for every node (when defined). It is better to use Control nodes instead, which are the building blocks for making GUIs and they handle input hierarchy automatically.
See how it works here: http://docs.godotengine.org/en/3.0/tutorials/inputs/inputevent.html#how-does-it-work

When using _input_event(event) on Control nodes, you can make it so elements in front will receive events but not their background siblings.

In rare cases where nothing else works, you can use this to stop event propagation: http://docs.godotengine.org/en/3.0/classes/class_scenetree.html?highlight=set_input_as_handled#class-scenetree-set-input-as-handled

answered Sep 4, 2018 by Zylann (27,004 points)
Welcome to Godot Engine Q&A, where you can ask questions and receive answers from other members of the community.

Please make sure to read How to use this Q&A? before posting your first questions.