Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
Issue ID
1199828
Regression
No
DragAndDrop state is not cleanup after a drag
This bug was originally reported on the #pyshotgun-facebook channel.
Basically the state of DragAndDrop is not properly reset after a Drag originating from Unity. If you would drag from another application unity AFTER a drag from Unity the objectReferences array is never cleanup. See video for repro clearer repro steps. This only happens on Windows.
0- Ensure you have a cube in your scene
1- Drag a material to an external application (ex: Visual Studio Code). This sets the objectreferences of the DragAndDrop class.
2- From the external app, drag any file (not the same you previously dragged) onto the cube
3- See that the material is assigned to the cube
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment