Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.2f1
Issue ID
892564
Regression
No
Buttons can not stay selected when the Event Trigger component is attached to a parent
Steps to reproduce:
1. Open attached project
2. Open the main scene
3. Play the scene
4. Hold the left mouse button on Yes/No buttons
5. Move the mouse a few pixels while holding left mouse button and still being in the button area
6. Observe the button deselecting itself
Expected result: The button should still be selected when the left mouse button is held and cursor is moved in the button area
Actual result: The button deselects itself when the cursor held down is moved
Note: When the "Event Trigger" component is attached to a parent object of the buttons, the buttons of that parent object lose the ability to still be selected when the cursor is held down and moved. This does not appear to happen when there is no "Event Trigger" component attached.
Reproduced in: 2017.1.0a4, 5.6.0f2, 5.6.0f1, 5.5.2f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment