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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment