Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0f1
2017.3.0b8
Issue ID
965712
Regression
Yes
[OSX] Double-clickling a script in the editor starts new instances of MonoDevelop
To reproduce:
1. Create a new project
2. Make sure that the external script editor in preferences is set to MonoDevelop AND that you have installed it together with Unity
3. Make a C# script
4. Double click to open it in MonoDevelop
5. Double click it again
Expected result: the opened MonoDevelop is focused
Actual result: new MonoDevelop instance is opened
Reproduced on: 2017.1.0f1 2017.1.0f3 2017.2.0f3 2017.3.0b8 2018.1.0a2 2018.1.0a3
Not reproduced on: 5.6.4p2
Notes: was able to only reproduce on macOS High Sierra 10.13.1, did not reproduce on 10.12.6.
Could not check earlier than 2017.1.0f1 versions, I could not create a script in those version.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
This is a duplicate of issue #964078