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
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
Add comment