Search Issue Tracker
Fixed in 1.1.2
Votes
37
Found in [Package]
1.0.7
Issue ID
1173165
Regression
Yes
[Mac] A new script is not being opened as a different tab when using VSCode
How to reproduce:
1. Create a new Unity Project
2. Make sure VSCode is set as a default text editor
3. Create two scripts
4. Open the first script, then open the second one
Expected results: Both scripts are opened in VSCode in separate tabs
Actual results: Only first opened script is shown in VSCode
Reproducible with: 2019.2.0a12, 2019.2.0f1, 2019.3.0a11 (package ver 1.0.7)
Not reproducible with: 2017.4.31f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0a11
Additional notes:
1. It was tested on OS X 10.14.2 and 10.14.4. The issue reproduces on 10.14.2. On 10.14.4 VSCode opens it's welcome screen only
2. Package versions 1.0.2 and 1.0.3 throw Win32Exceptions on a Mac, however, the issue does not reproduce
Resolved in package version 1.1.2
Comments (12)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
- "Multiplayer Center" window does not reflect changes made in "Other Packages" section
- Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
- Editing and saving Curve changes in UI Builder window throws multiple errors in the Console
- [UI Builder] Value is not selected when left clicking on Spacing/Border Widget values
juanfornos
Aug 06, 2019 17:37
Same bug issue here. It was introduced with Unity 2019.2 (I guess with the new VSCode package). Worked perfectly on Unity 2019.1
moncastro
Aug 05, 2019 08:16
I can confirm this bug as well.
It works proper only while first open from Unity Editor, then if VSCode is running (even on the welcome page without loading any solutions), clicking on scripts or on console errors only changes the focus to the VSCode window and that's it.