The community has been asking for an updated MonoDevelop for years (literally), and Unity has finally shipped a new version! What do you think?
Let’s use this thread to discuss impressions, tips, problems or whatever else related to the updated code editor.
To get the ball rolling… as a unityscript user, I have to admit I’m a bit disappointed so far.
Although the editor is slightly faster (a bit noticeable when scrolling through large files), some previous features are no longer working!
Specifically, the pads “Document Outline” and “Classes” are not showing unityscript/js files. These both work in 2.8.x and are extremely useful for quick access to files and their functions, etc.
Other than that, I haven’t really noticed any obvious differences, apart from the ui looking more like xcode.
Is this update as big a deal as we’d hoped? Maybe it is better for c# users.
So unimpressed with 4.0.1, I reinstalled the old MonoDevelop 2.8.2
Gone is my useful toolbar, to be replaced with a huge realestate eating panel of things I don’t use, and still it didn’t allow the one thing I wanted, which was multiple instances.
In response to the announcement of the MonoDevelop upgrade I was figuratively dancing a jig.
Upon starting the debugger however it appears Mono itself hasn’t been updated. It’s still not possible to view the contents of generic collections when debugging.
Unknown type 'System.Collections.Generic.CollectionDebuggerView`1, mscorlib.dll'
The previous version of Unity was crashing after hitting a breakpoint in MonoDevelop. Has this been fixed? It’s been pretty brutal trying to debug without being able to hit breakpoints in a debugger.
I like the new way it handles debugging, and the modernised look. Some of the other changes seem like improvements, but will take a bit of getting used to.
However, I’ve found it absolutely riddled with bugs, and am here looking for solutions. Looks like the post popular one is to downgrade back to 2.x.x.
I think I might do that, and try again in a month or two. Anyone else been having issues?
(Using with Unity 4.3 on WinXP - upgrading to Win7 at Christmas)
I think it’s awesome just because it is SOOOO much faster on OSX. Previously monodevelop could hang for 20 seconds randomly, which was very annoying. And also it could take several seconds to load the autocompletions. And yes, I did disable all plugins.
So this new version is really nice to work with.
Now I can actually use the Command+Dot search functionality in practice, in the previous versions it has been so slow that it was almost faster to look through all files for the correct one, refactoring doesn’t seem to take an extremely long time either.
The new MonoDevelop seems to have also lost the Row/Column indicator at the bottom right of the window.
Anyone know a way to find out your column number now?
Also on OS X, debugging is very painful, like in the old days…
I always crash Unity after or before breaking on a breakpoints, this is really inacceptable on a professional developing tools!
I 'am surprise to not read much about this here… Is it the same under Windows ?
What is your workaround to debug ? Do you open Monodevelop and then unity ?
Having same issue, Logitech Performance MX. Monodevelop 4.0.1.
This is really messing with my zen thing.
I’ve always been happy with Unitron because that is the specific code hinting / highlighting I learned on. I’ve been trying to make the switch to Monodevelop and now that i’m forced (since they finally killed Unitron) and now simple scrolling doesn’t work… eish. :neutral:
Would upgrading to Mavericks work? Different drivers there?
PS, any way to get monodevelop to “look” just like Unitron did for .js?
If your on a laptop, use the trackpad to scroll, then use your scroll wheel in the same window. Seems to work for awhile with my MX. Weird. Also kinda works when you click the scroll wheel in as you scroll.
I switched back. The missing toolbar was annoying, but I could live with it (although the space is still used for… nothing). But the real killer was the fact that every time I saved (control-s), the scroll bar would jump up by about a page, and I would lose where I was.
