I really hope it will get some more priority and be included in the next hotfix. On slower PC’s this all takes quite a while and when having to add multiple classes the amount of time requires for simply adding C++ classes quickly adds up to enormous amounts of time/annoyance.
Actually it opens TWO additional new VS instances (at least for me with VS2017 and running the UE4-editor through VS2017 on Windows 10 Pro):
- Add a new C++ file in editor
- The new VS2017 instance throws an Intellisense error. Close the new VS2017 instance right after it displayed that error.
- The UE4-editor now opens yet another VS2017 instance (only containing the newly added C++ file, not the project I believe)
- Close this third VS2017 instance and the editor indeed has a stuck “Loading Visual Studio” toast message.
- Give focus to the original VS2017 instance and click the option to reload the project there from the popup because the project has been changed outside of this VS2017 instance (this will close the UE4 editor instance)
- Optionally: Relaunch the UE4 editor by pressing F5 to build&launch it.
Now you can finally work with the new file. Especially on slower PC’s or when I need to make an interface + baseclass for the actual class I need… Takes about 12 minutes on the slowest we have here…
Also I’m not sure how smart it is to ignore the stucked toast message before adding another file. I usually just restart the whole thing to be safe. But it eats my sanity so now and then.