Nicholas Lawson

Yes, the way I see it there's some short term fixes we need to apply that we can do immediately and quickly (low cost) to fix the workflow bugs like...

I gave some of the scenarios above. All of those scenarios are currently possible to happen.

Also bear in mind that there are ways to achieve all user intents: * User can drag the fbx itself to the viewport * User can **expand** the fbx, then...

Well the current behavior shows the "No Entry" sign by default by telling the operating system that there's nothing in the data that can be dropped there. (The operating system...

Note that the above PR isn't going to 100% solve all problems with dragging stuff around. But at the very least it should stop dragging stuff causing duplicate mesh components...

I'd recommend adding additional tickets for e.g. improving the way we generate procprefabs (ie, making it possible and easy to generate default procprefabs even with scene settings present), as well...

I committed the first wave of drag and drop improvements. I'm not sure it address _everything_ in this Issue, but perhaps this should be split into pieces of achievable work...

> Could we add any automation tests for this change or do we plan to backfill the tests in future PRs? The multithreaded regexing would already be covered by existing...

turns out multithreading regex is slower on windows even if its a tad faster on Mac. I'll strip that out. the other thing I can do is convert regexes to...

I added a test to cover the new API that pre-warms the excluded folder cache, and de-recursed the file scanner, allowing the caching of more things. I also added a...