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

Area2D + CollisionShape2D: inconsistent mouse_enter & mouse_exited events at window border #57723

Closed
Sauermann opened this issue Feb 6, 2022 · 0 comments · Fixed by #58610
Closed

Comments

@Sauermann
Copy link
Contributor

Sauermann commented Feb 6, 2022

Godot version

v4.0.alpha.custom_build [79a4d78]

System information

Debian 11, Vulkan

Issue description

As a prerequisite, have an Area2D + CollisionShape2D touch the window border.
Now move the mouse from within the Area2D to the outside of the window.
Regularly the final event, that the Area2D receives is mouse_entered.

I would expect that the final event is mouse_exited.

Could be related to #57588, but the triggered events are different.

I also verified that this issue happens on

  • Windows 10, v4.0.alpha1.official [31a7ddb]
  • Debian 11, v3.4.2.stable.official [45eaa2d]

Steps to reproduce

  1. Load and start MRP
  2. Move mouse cursor between inside and outside the window
  3. Notification on screen and in the console indicate the most recent received events.

Minimal reproduction project

For 4.0: BorderPhysics.zip

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

Successfully merging a pull request may close this issue.

2 participants