Unity 3.4 opens scripts with Monodevelop - Uniscite not longer the default editor?

I was used to work with Uniscite. But with Unity 3.4 it is not longer the default editor. To my surprise the Monodevelop editor opened up when i clicked at a script. Is this intended behaviour? Is it planned to remove Uniscite? Do i need to work with the Monodevelop Editor now?

 

Yes, it's intended. No, you don't need to use Monodevelop; as always you can choose the desired editor in the preferences.

--Eric

 

monodevelop now works properly with js - making me a very happy monodevelop user. The drop down selection of your functions etc alone is a huge timesaver

 

The freezes caused by that not though -.-

Thanks for help

 

Freezes? my cpu is 6 years old and its smooth as a babys butt. Must be something odd going on, cos it would be nice if you could get it running smoothly. I have all the random stuff of monodevelop disabled so it looks like uniscite.

 

I agree. Mono is better but reason i seldom use is it clashes with my visual studio. I guess a bug in the 3.3. Hopefully it's fixed.

 

I cannot nail it down really, but i notice short annoying freezes here and there. And i have a relative new quad core here, half a year old. My guess goes to all this fancy stuff at once, like this autocomplete dropdown list. I will have a look how it behaves when i turn most of those things off. Maybe that helps

 

I put it on most compact and remove all the fluff... hope it helps. Maybe defrag your HD?

 

I have no issues with it and Visual Studio installed... my laptop is 4 years old and it runs really well.

 

Where can I find the Uniscite editor?
answer:
C:\Program Files (x86)\Unity\Editor\Data\Tools\UniSciTE


Wow the whole Monodevelop destroyed my project in under 5 seconds. Its calling for errors on Unity scripts that I have never even touched listing errors that make no sense what so ever.

Its even locked out the project folder so I cant restore it from yesterdays back up.

I dont know what is going on, so I managed to restore the folder and I'm still getting the same errors.
Mind you I am posting here because none of these errors started until I double clicked a script to edit it and it opened MonoDevelop, which as it appears to me, has blown apart all the libraries or something.

Now Ive got errors for two Unity-written scripts, that I'm not even using.

Assets/Standard Assets/Image Effects (Pro Only)/DepthOfField.js(139,21): BCE0005: Unknown identifier: 'it33'. (About 15 or so errors on this script)

(13 various errors of similar type on this script below)
Assets/Standard Assets/Character Controllers/Sources/Scripts/ThirdPersonController.js(325,33): BCE0048: Type 'Object' does not support slicing.

(5 or 6 errors with this script)
Assets/Standard Assets/Character Controllers/Sources/Scripts/ThirdPersonCamera.js(141,9): BCE0005: Unknown identifier: 'currentHeight'.

Like I mentioned, the project was literally working fine in 3.4 until I opened MonoDevelop to edit a script, I ran it and played it.

I 'Guess' I will try and delete these scripts and hope that works, since I am not using them anyway.

Well that didnt work, it made matters worse.

Now I need to go back to 3.3

Thanks.

 

I switched back to UniSciTE because MonoDevelop was slower to open (I have an i7 950 so I doubt its my machine) and found that the word highlights are gone, it no longer highlights in blue things like Update or transform, it still highlights function though. Can I turn this back on somehow? Is this the same for anyone else? I found it very helpful for things like spelling.

 

Word highlighting is gone for me too. This is a nightmare as I'm still relatively new to scripting and I can't tell what's wrong with my code anymore.

 

If you still have your 3.3 Unity around, you can install the UniSciTE from that folder and you will get the highlighting back again. (At least I did on mine)

What has gone completely, and this has also gone with Mono is that if you got an error with a line number.. clicking on the error used to take you to that line, now it just takes you to the first line of the script.. nightmare!

Oh yes, and just an aside, with a quad core machine and 8 gig of Ram when I open unity with Mono enabled and click on a script to open it, I can wander off and get a few things done before it opens.. or so it seems.. I timed it at 48 seconds to open Mono... not good.

Regards

Graham

 

I just noticed that with the line numbers! Argh!

Not fun at all. Does anyone know where I can download 3.3 for the editor?

 

makes me laugh all these coders crying their scripts don't work. Guys, your scripts were broken to begin with... and going back to 3.3 will only introduce more bugs you cannot detect because #pragma strict isn't enforced. Why do you do this to yourselves? seriously, just define your vars properly, thats the only reason they break.

Unity is just as much to blame here for having examples that didn't define vars properly.

Don't go back to 3.3. You're only harming yourselves, end of story.

 

You aren't reading the thread. This has nothing to do with declaring variables - I do that religiously and have had no errors except for the one caused by textboxes no longer accepting input. This has to do with the UniSciTe editor no longer:

1) highlighting words
2) opening to the correct line when you click an error

 

Argh, no, that's just wrong.

1) #pragma strict is not enforced generally in Unity 3.4, it's only enforced if you're using iOS/Android--which was always the case anyway. The only difference now is that #pragma strict is effectively added to scripts automatically in iOS/Android, whereas before, it waited until you made a build before enforcing it.

2) This thread isn't about "defining vars properly", which doesn't have anything to do with #pragma strict anyway, and isn't the reason scripts break.

--Eric

 

When i use monodevelop as editor, it complains about line endings in my scripts and i cant open them. I never worked with monodevelop before, how do i fix this issue.

 

MonoDevelop does seem to open to the correct line of an error for me, however it only works occasionally (sometimes I'll have to double click the error 5+ times for MonoDevelop to do anything). Same with opening Scripts in the Project panel or Inspector, it will take a few attempts until MonoDevelop opens the script. Quite annoying, might go back to UniSciTE for now.

 

Sorry Aubergine, but i fear this is the wrong thread for this question. I would suggest to open your own thread before this question vanishes in the rest of the answers here.

That`s a real bummer that Uniscite doesn`t highlight the wrong words anymore nor jump to the error line automatically. Seems that the Unity crew really wants to force us to leave it

Monodevelop is a slow snail compared to Uniscite. I would never really be happy with that one as the code editor. It takes around 10 Seconds to open up Monodevelop here. This may not be this much, but it adds over the time, and breaks the workflow. And this annyoing dropdown boxes in the text makes me crazy. I hate it. Uniscite opens in an eyeblink, and doesn`t have this much lametta.

Hm. I`ve grabbed the Uniscite folder from 3.3 (my laptop was luckily still with 3.3), have replaced the Uniscite folder in 3.4 by that. And the problems remains. This means the problem is at the Unityeditor end, not the Uniscite end. And so there`s nothing we can do about but asking for a fix. Who wants to submit the bugreport?

 

Yeah it's very frustrating, and your very right about the break in workflow! MonoDevelop is fancier, but I don't need that if its this slow.

Does anyone know if MonoDevelop did the highlights before 3.3? Because it dosn't in 3.4, meaning that your likely right and it is the Unity Editor if Monodevelop is missing the highlights too.
I'm not sure its a bug, but I'll send a report anyway,

-Chris

 

Monodevelop uses a more generic, language based highlighting for C# (and I assume it does the same for JS), which won't include Unity API functions. While I understand that takes getting used to if you haven't used something like Monodevelop before, it is more in line with other development environments (but I can totally understand people not caring about that at all ).

In return for losing the Unity API highlighting, you get code-completion, which (once you learn to work with it) is much, much more powerful, as you no longer even need to type the whole keywords or function names anymore.

I would really recommend trying to learn to work with Monodevelop, because functionality such as code completion and refactoring are huge timesavers when used. But then again, this is coming from someone who can't think of Uniscite without replacing a certain 'c' by an 'h' .

It is slow to open, that is true. However, if you don't close Monodevelop after editing (keeping it running in the background), opening files is as fast as it is with Uniscite or Unitron; at least it is for me.

 

You're supposed to let MonoDevelop open after you click "Sync MonoDevelop Project".
It's pretty obvious that MonoDev takes longer to open than Uniscite does, it is designed for you to work on a whole project, not a single script at a time.

And all those errors showing up since update, I haven't seen any of them by myself. I feel lucky.

 

UniSciTE had and has the auto complete, so its not really a trade off :/ Thats a good suggestion though, about keeping the scripts open,I'll try that and see if it remedys the workflow, thanks

 

MonoDevelop is really suited for dedicated coders, whereas many Unity developers are individuals who also play the role of designer and artist. It also takes up a ridiculous amount of resources.

MonoDevelop does not select the proper line from errors, nor does it highlight anything other than standard JavaScript keywords. I have since switched to N++, which I've been able to customize to highlight words. Still no error line selection, though.

 

Why does monodevelop select the correct line for me? it never misbehaves so far. I've much bigger problems with unity constantly crashing and annoying the hell out of me. It is simply not stable on the PC.

 

Perhaps I'm wrong, but what I remember from Uniscite is that it would only autocomplete within a file and probably Unity API calls. MonoDevelop autocompletes everything, from calls to the mono API to functions from other scripts. It will also list all the possible function and variable options right after typing a dot, which helps a lot if you forgot the precise name of the function.

 

I hate autocomplete. It is the wrong word for 90% of the time anyways, and just slows me down. Not just because the editor may freeze for a short time period to pop up the autocomplete (that`s what Monodevelop is doing here very visibly, eating the one or another letter that i already typed in, i`m a fast writer) , but also because it breaks the workflow. The time i spend to check if autocomplete is on par with me is better spent in typing the word in that i want to type in. I am faster that way. It can be a good thing when it works. But for me it just disturbs.

 

Ok, Monodevelop is driving me crazy! I am not sure what I have done, but in Javascript the Fold is working now, was not at first. But..
Now it opens with the cursor in a block mode, where i can't do anything, but if I hit the A key, it then show -- INSERT -- at the bottom.
(found this by accident) So Insert mode is ok, but then it goes back to that block mode.. What did I set or why is this now such a pain!?

I used to user SHIFT plus the arrow keys or EOL or END to hightlight text to copy, now that does not work...

Its so different, its slowing me down big time... Is this just me or is the learning curve worth it in the end ??

 

I also think this is bad. Not highlight the error you get is plain stupid. This should be a high priority.
Also its slow. slow to start up and I hate when I open up one script it also open up all the others. maybe its some settings in it I need to turn of.
I did try this program in 3.3 and i did switch back very fast.
Now im stuck with it and its one of the worst program i have used. so i dont see why some think its great.
Even start up the whole dam Visual studio is faster and it also alot more advanced.
So why the change to this junk program?
I think i will use notepad++ instead. its doing the work alot better and its so much faster.

 

My main issue with MonoDevelop is how slow code completion is. Maybe my project is just too big but it takes a good 2-3 seconds to pop up the code completion options, all the while freezing the display. It does it just about every single time I start typing anything, therefore the text appearing on my screen is like a slideshow. You have to just type through the stall and your text will show up, but it's so annoying I just completely disabled CC. (Core i7 @ 3.6GHz, 12GB mem, Vista-64)

Other peeves:
- Monodevelop always uses Mac/Unix line endings. All of my scripts are windows line endings. If I work with them in Notepad 2, I have it set default to Windows. So every time I do something back and for I get those annoying error messages.
- It doesn't highlight the Unity property names anymore.
- SERIOUSLY annoying auto-case-sensitive search issue

I've never had any crashes or stability issues like I see some others have. I've never had any problem it jumping to the line of the error on a double click in the console either.