Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Click Events passing through Buttons if there is a Viewport underneath #39666

Closed
Aidan-85 opened this issue Jun 19, 2020 · 3 comments · Fixed by #58334
Closed

Click Events passing through Buttons if there is a Viewport underneath #39666

Aidan-85 opened this issue Jun 19, 2020 · 3 comments · Fixed by #58334

Comments

@Aidan-85
Copy link

Aidan-85 commented Jun 19, 2020

Godot version:
3.2.1.0

Issue description:
Clicks seem to pass right through a Button without triggering it if there is a sub Viewport underneath the area of the button that's clicked. It happens even if the Button has a Mouse Filter set to 'Stop'. If there's a Button within the Viewport, directly below, it receives the Event without a problem.

Steps to reproduce:
Place a button partially over a sub viewport and click area where they both overlap.

viewport_issue_1
Viewport_Issue.zip

@g-mcclock
Copy link

g-mcclock commented Jul 18, 2021

Godot version:
3.3.2 Mono

This has become a big issue for me too. What makes it especially tricky is that it seems like any node inside the viewport can block input to a control as well, even if the viewport itself doesn't cross boundaries with the control.

For example, If button 2 is inside a viewport, with button 1 and 3 adjacent, everything works as expected.
all_working

But if I then drag button 2 e.g. upward inside the viewport, then button 2 blocks input to button 1, EVEN THOUGH it's not even onscreen and should be contained by the bounds of its viewport.
interference

This also occurs if you drag button 2 down toward button 3.

Here's a sample project in C#/Mono
ViewportBug.zip

@Sauermann
Copy link
Contributor

This bug report has two duplicates: #45400 and #48401

@Reneator
Copy link

Still happening in v3.5.stable.official [991bb6a]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment