You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
area_entered and area_exited signal is propagated at the same time when setting Area.monitoring = true [or false]
only area_entered is expected when setting Area.monitoring = true and
only area_exited is expected when setting Area.monitoring = false
I think you are misunderstanding this issue. What you do here is toggling the "monitoring" property of box, while listen to areas that enter/exit ray.
What happens internally in the physics engine as you do this is that the object is added and removed from the space (this is needed so pairing can be re-created). As it is correct that the ray shape will sill monitor it, you get an exit/enter pair of signals.
The "bug" here may be that an optimization could be made within the physics to realize the area exited and entered and simply send nothing. Still the state remains correct.
IMO this is too low priority to fix now, as it's not exactly a bug, so kicking forward.
The "bug" here may be that an optimization could be made within the physics to realize the area exited and entered and simply send nothing. Still the state remains correct.
The solution you mention sounds incorrect as you describe it.
What if an object moves "fast" through a small area. The programmer/designer still expects to see that something entered and then exited that small area. Ignoring a pair of enter/exit is very confusing.
Godot version:
3.1.beta 973b68f
OS/device including version:
Kubuntu 18.10
Issue description:
area_entered
andarea_exited
signal is propagated at the same time when settingArea.monitoring = true [or false]
only
area_entered
is expected when settingArea.monitoring = true
andonly
area_exited
is expected when settingArea.monitoring = false
probably related to #22889
Steps to reproduce:
Minimal reproduction project:
area monitor.zip
The text was updated successfully, but these errors were encountered: