The completion in MonoDevelop is so slow I turned it off anyway. It stupidly tries to complete when you've only typed one letter, which of course produces too many results. It also doesn't abort/restart the completion analysis when another key is entered. I sometimes typed 20 characters before anything appeared on screen.
Hopefully Unity will fix one of these ASAP.
answered Jul 30, 2011 at 04:53 AM
This threat is quiet old but I'm just replacing the slow-mono-editor and stumbled over this question:
unity, is not doing autocompletion for some reason, even when I tried turning it on (manually in the SciteGlobal.properties-file). Help for the mysteriously missing auto-completion is missing on the homepage, since Scite seems to be discontinued and Geany shall become the editor of the future (unfortunately without official unity-support).
However, I got notepad++ running well with unity and the mentioned tutorial.
to be downloaded manually. It's a zip-file containing two dll-files. Extract it into the plugins-directory in the notepad++-folder and remove one of the two files not needed (depending on your notpad++-version). Otherwise notepad++ will complain about one of the two files on startup, since one is for Unicode- and the other for the ANSI-version of notepad++.
Plugins >> Language Help >> Options >> Add and fill the three fields (as mentioned in the tutorial):
Afterwards, enable the checkbox "Enable showing this entry in notepad++ help menu" below.
To test it, doubleclick on a keyword in a script and right-click then. The context menu will show the entry "Help". This entry will open the unity-documentation in the web-browser with an explanation of the selected keyword. Since the Language Helper also supports CHM-helpfiles, such a solution would be a lot more elegant. Unfortunately I don't know of any offline-helpfile-version of the unity-documentation. If there should be one, maybe someone can post a link here.
The notepad++-tutorial however, has one minor issue:
Script Editor Helper" is not working with the newest unity-version anymore. The file shall get renamed to MonoDevelop.exe to replace the original Mono-Startup-Program. This way, a script's line-number (on a compilation-error in unity) shall get forwarded to notepad++ instead of starting mono. This is not working anymore since Unity starts mono with calling some dll-file, in the newest version.
Hence, jumping to an error's line in the script-editor is not possible anymore with some other editor than mono. Since notepad++ supports line-jumping with the "-n"-switch on the command-line, this is a real feature-lack in unity: The settings allow usage of another editor but no command-line-arguments.
answered Dec 31, 2011 at 08:57 PM
Sorry for my late response... A lot of time has passed and MonoDevelop turned a lot better for java than was before, thus, I got used to it. As I told before, I tried to install many script editors in vain, but I didn't tried again since then because as I said, I got used to MonoDevelop. However, I think that following the steps that Spacepilot mentioned it would probably work, and I sure will try someday.