Search Issue Tracker
Duplicate
Votes
23
Found in
4.3.1f1
Issue ID
579055
Regression
Yes
When opening MonoDevelop, 2 instances of one script are opened
To reproduce:
1. Open attached project. It contains two scripts
2. Open both of these scripts in monodevelop
3. Try to open either of them while monodevelop is still running - everything works fine, only two scripts should remain opened
4. Close monodevelop
5. Open either of the scripts - two instances of the same script are opened, so three scripts are now present in monodevelop
Does not occur with monodevelop in Version 4.1.5f1
Duplicate case: http://issuetracker.unity3d.com/issues/md-opens-same-script-two-times
-
sebastiansgames
Jul 17, 2014 03:59
This definitely happens quite often with my Mac version of Unity Pro 4.3.4f1.
-
Adam Romney
Apr 17, 2014 14:48
I observe this issue on the free Windows version at home. I have never experienced this with the Mac Unity Pro install.
-
Kazimieras
Feb 06, 2014 11:49
This issue causes "jumping" cursor (caret) issue in MonoDevelop after saving one of the script instance.
If you have opened two instances of the same script in MonoDevelop, edit something in the first instance and save your changes. Remember in which line cursor was placed. Go to the other instance of the same file, edit your script on different line and save it. After saving, cursor usually jumps to the line where it was placed on the first instance.
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
- OnTriggerExit2D events are not triggered when disabling Collider, despite "Callbacks On Disable" being enabled
- [Android] [Vulkan] UI that is activated after a delay flickers when a Scriptable Render Pass goes over it
- [Linux] Characters are converted to Latin letters when using IME on Linux
- [Ubuntu] Possible for Create menu to show sections with no options inside
- [Usability] Not possible to set Editor Window text colour to be default black without workaround
This is a duplicate of issue #588452