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
- 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