Code folding is still broken!

What the heck is going on?

http://answers.unity3d.com/questions/574075/monodevelop-401-unity-43-code-folding-bug.html?page=2&pageSize=5&sort=votes

This question is dated just over a year ago. Why is this still around? The monodevelop version in unity 4.5.5f1 is still the same as the one quoted there.

I’m trying to bring in a friend to join my team and his opinion of unity is already low enough without the default toolset being broken.

Someone please explain this situation to me. Whose responsiblity is this, why isn’t it sorted yet?

Don’t use the default toolset than, visual studio does this just fine using both scope or user defined regions.

that’s not really the point, is it? the tools provided with unity should be bug free, as far as possible. Certainly a year is more than enough time to fix such a general bug which most people are working around.

Even more to the point, one of the comments there mentions that this is a new bug and did not exist in unity 4.2

So why was the built in editor updated to a version that obviously wasn’t stable, and then left there for a year. why wasn’t immediately either fixed or rolled back? I’m assuming that monoevelop is a third party application, someone please fill me in here.

Did you submit a bug report to make the developers aware of the issue? What is the case number for the bug?

What? no, of course i didn’t, the issue is known since over a year ago. It would be absurdly naive to think nobody had filed one by now.

And indeed they did, just short of a year ago: http://issuetracker.unity3d.com/issues/monodevelop-4-dot-0-1-doesnt-allow-folding-of-classes-slash-methods

I don’t see any comments from unity staff there, any acknowledgement or update on the issue. It’s marked as a regression too, shouldn’t that get it some priority?

And another one: http://issuetracker.unity3d.com/issues/monodevelop-with-4-dot-3-loses-code-folding-on-save

Hey look, it IS a third party program. And unity is a whole first increment behind of the version number: Redirecting…

The current version no longer has this bug, i’m using it right now.

So what’s the deal here UT ?