Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.3.4p4
Issue ID
797221
Regression
No
MonoDevelop does not pop up after error is double-clicked in the console
Steps to reproduce:
1. Create new project
2. On the top menu select Edit > Preferences > External Tools and set "External Script Editor" to MonoDevelop
3. Create a script and write a line of code which would consist an error and save it
4. Focus to the editor and double click on the error in the console
5. Note that MonoDevelop logo starts blinking in the start bar (see attached gif)
Expected behavior:
After error is double-clicked in the console, MonoDevelop should pop up with the focus to the according error
Actual behavior:
MonoDevelop logo starts blinking in the start bar and does not pop up
Note: This happens only if MonoDevelop is not minimized
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment