Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
We need an object browser for iLogic, just like the one that can be found in the API window. This would make complex iLogic programming much easier, especially for beginners.
We need an object browser for iLogic, just like the one that can be found in the API window. This would make complex iLogic programming much easier, especially for beginners.
This would be great. We have often resorted to pulling up the VBA editor first while working on an iLogic rule, just to get access to information like this. It would be a big improvement to have this kind of help more accessible from the iLogic editor.
IntelliSense is the general term for a number of features: List Members, Parameter Info, Quick Info, and Complete Word. These features help you to learn more about the code you are using, keep track of the parameters you are typing, and add calls to properties and methods with only a few keystrokes. See Visual Studio by Microsoft as an example.
I don't no if it means anything, but it doesn't seem as we got all the "Kudos" from the original post regarding the "iLogic Intellisense" when the posts were merged
In stead of making all this from scratch, perhaps it could be implemented in a way, where you could use Visual Studio Express as Rule Editor? And a user setting to control wether to use "Classic Rule Editor" or "Visual Studio Express if installed".
I know this thread has been sitting here untouched for more than a year, but maybe there's some life here!
The so-called Object Browser is in fact a class browser. OK, that's worth something.
Would it be valuable to have a different kind of "browser" that showed the live Inventor API object model, with the appropriate current values of all (API) properties, starting with the Application object and going through the whole hierarchy from there? As I envision it, you'd see the values for properties, but no values for methods (needing arguments). You'd be able to "copy" an appropriate code-snippet to get any property or method. It would be a complete reference starting from the Application object, or maybe the document or componentDefinition, and so you'd probably have to delete some text from the front of the snippet in order to really use it.
Here's a very rough idea of it. Not exactly how we would do it, just showing this to encourage some ideas. In this example, you're "in" a part, and you are browsing through the first of 5 extrude-features:
