MonoDevelop's release cycle isn't linked to Unity's release cycles. It's made by a completely separate bunch of people. I have run into a number of previously reported issues with the version of Monodevelop that shipped with 3.5.1 version of Unity on the Mac. 1) Editor frequently goes to 100% CPU - edits are becoming a real pain. Visual Studio for Mac builds on top of MonoDevelop, adding open sourced internals from Visual Studio and many new extensions to support new workloads. MonoDevelop's speed has been an issue for some time—especially its load time, which takes ages on my MacBook Pro with its SSD. Hell, it takes longer to load than MS Word! Personally, I just use Unitron for smaller projects. It's still installed with Unity; you just need to change the Unity preferences to use it. What it lacks in features, it more than makes up for in just plain working properly. (Also: BBEdit or TextWrangler can be made to work with C# code. The necessary file can be obtained from ) Unfortunately, only Unitron and MonoDevelop are able to 'see' the Unity API as well and pop-up the relevant helpful info. Which is a shame. You'll probably want to have the Unity Scripting Reference pages open somewhere while programming. I'm now using Unity 4.0 on the Mac, and this is still happening. This has been an issue for a long while now. Why hasn't this been fixed? I understand that the Unity version of MonoDevelop is a special build, but there have been 26 separate releases of MonoDevelop between the version Unity provides (2.8.2) and the current stable release (3.0.5). When can we expect this issue to be resolved? Refactoring and finding references is very, very slow. It just took 2m 38s to search the solution for references of a class method that is only called once. This is insane. I'd like to be able to safely refactor my projects without waiting *minutes* for it to respond. Please fix this! I'll happily work with Unity developers, if they are unable to reproduce the issue locally. Click to expand.That does not help much. UT made custom modifications to their MonoDevelop and forked it long ago which makes it quite a bit more complicated to update it to the real thing. Unity at the time runs on an MD base thats very old, potentially even dating back to pre-Xamarin days which is huge given the massive boost mono got since Oracle killed mono inhouse after the Novell takeover forcing Xamarin into existance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2018
Categories |