Search Issue Tracker
By Design
Votes
0
Found in
2022.3.62f1
6000.0.49f1
6000.1.3f1
6000.2.0b2
6000.3.0a1
Issue ID
UUM-105677
Regression
No
UGUI Pointer Enter/Exit does not always trigger when hovering quickly over it
Reproduction steps:
1. Open the attached “IN-101948.zip” project
2. Open the “Scene” Scene
3. Enter Play mode
4. Hover quickly over the squares side to side
5. Repeat the hovering a few times, fast
6. Observe the color of the square
Expected result: After the cursor leaves the square, its colour is red (means exit was triggered)
Actual result: Sometimes the color of the square remains green (means exit was not triggered)
Reproducible with: 2022.1.0a1, 2022.3.62f1, 6000.0.49f1, 6000.1.3f1, 6000.2.0b2
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- Also reproduces in the Player
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note:
The repro project scene is not set up correctly to make proper use of the hover hierarchy. If you want the "Image (exit)" GameObject to be around the "Image (enter)" GameObject and act as an exit barrier that catches the Exit event for the inner object, you need to make it a parent of the inner object.
As it stands in the repro project, the "Image (exit)" GameObject is a sibling of the "Image (enter)" GameObject, which makes it only receive an Exit event if it had previously received an Enter event, which is not guaranteed to happen if the "Image (enter)" GameObject blocks it for every frame that the mouse moves over it.
Yes, frame rate will have an impact on this behavior. It's the project that's not set up correctly. Worst case, just add an invisible parent that matches the larger object's dimensions and catches the exit events for the inner object.