Search Issue Tracker
Fixed in 2020.1
Fixed in 2019.3
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
- Rendering is broken with UIToolkit with many Intel GPUs (driver-bug)
- [Vulkan] Crash in Windows Standalone when Vulkan is set as rendering API and player window is out of focus
- "Can't destroy Transform component" Error is thrown when closing a scene that contains a DontSave Prefab with a Child
- [Particle System] Editor freezes when assigning a nested Particle System in the Sub Emitter Module
- Unable to switch to different material when selecting another material from Asset selector window on Particle System Material
Add comment