uIntelliSense brings all the power of IntelliSense code hints to your Unity code.
Have you ever forgot the exact meaning of some method parameter, or stumbled upon a method you’ve never used before? Don’t you think that searching through Scripting Reference is way too much work when all you really have to do is to hover over the code with your mouse?..
And this is exactly what uIntelliSense is about, providing useful hints for the Unity API — descriptions for types, variables, methods, method parameters etc.
Once you’ll try it, you’ll get used to it immediately. It is extremely helpful and time-saving, especially if you are a beginner who doesn’t knows the Unity API very well.
Second part of uIntelliSense is a Visual Studio extension for Visual Studio 2012 and newer, for even better experience: in-IDE integrated Scripting Reference browser, Quick Search for Unity API and more! See details in the PDF manual below.
Unity 4.6.x - 5.x, both Windows and macOS editors. Pro license is not required.
Support:
For any questions regarding this plugin, feel free to contact me at contact at lostpolygon.com or post in this thread.
If you like the asset, please review/rate it on the Asset Store, I’ll greatly appreciate that
i am very interessted in your asset. I really like this kind of intellisense. I have one question. Is the tool creating the intellisense file out of the actual API (I can allways create an up-todate one) or do you have to maintain the asset with every upcomming change (Unity 4.6 or 5.0)?
Yes, it generates the data from the documentation of Unity version it is running on, so it is always up-to-date by design. It already works as-is on 4.6 and 5.0 beta (though some documentation files are still missing in 5.0 beta, but that’s not my fault, and it doesn’t really affects the output). Probably someday Unity will decide to change the format for documentation, and then I’ll have to do some specific fixes to support future versions, but as it is now - it just works.
When using UnityVS you have to add it to every project right? Will this ever change?
I assume you should run the index creation every major release of Unity so it can update the documentation?
Yes, you have to add it to every project that uses UnityVS. It is unlikely to change, as this isn’t something I can fix at all because of how UnityVS works. It maintains it’s own version of VS project with its own incomplete version of documentation data, so uIntelliSense needs to be present to prevent UnityVS from doing this.
The documentation data is saved in Unity installation instance from which you run uIntelliSense, it is not global. Basically, you have to regenerate the documentation data for each Unity release you use. This isn’t something I can fix either because of the way IDEs detect documentation data.
Just tested it and it doesn’t seems to work. This is not an issue of the plugin, though, but of quirky IntelliSense implementation for UnityScript on MonoDevelop. C# works just fine.
Strange. Do you have the menu item? Tools → Lost Polygon → uIntelliSense
What Unity version and OS do you use? Could you please try creating a new project, import just uIntelliSense into it and try again?
It should, actually, and it always worked for me and for a lot of people, but apparently it doesn’t sometimes… I’ll try to investigate the reason, but meanwhile - once documentation data is installed, it’ll work in every project (exception is if you use UnityVS, in that case you’ll have to keep uIntelliSense inside the project).
