Search Issue Tracker
Fixed in 4.6.X
Votes
0
Found in
4.6.0b15
Issue ID
623643
Regression
No
Setting "interactable" property in script has opposite results
To reproduce this bug:
1.Open the attached project
2.Open "Scene".
3.In the Hierarchy, select the "Button" object.
4.Make sure you have an Animator window open to watch the state transitions of the Button.
5.Press "Play" to start the scene.
6.In the Inspector, scroll down to the "NewBehaviourScript" component.
7.Toggle the "Interactable" checkbox on the NewBehaviourScript on and off multiple times.
8.Notice how when the checkbox is checked, the Animator (and Button) is in the Disabled state. Also notice how when the checkbox is unchecked, the Animator is in the Normal state.
9.Also notice how the "Button" component's "Interactable" checkbox appears to be the same as the NewBehaviourScript's checkbox.
10.If you disable the NewBehaviourScript component, and then toggle just the Button's "Interactable" checkbox, you'll notice it performs correctly.
11. Additionally, if you hover over the button after toggling the NewBehaviour script “interactable" property, that seems to trigger the button to update its transition state to the correct state
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
- [Linux] "Error while reading movie" errors are thrown when opening templates
- Shader warnings are being thrown after building Mixed Reality Template
Add comment