Where to start? Inventor iLogic vs API

Anonymous — Fri, 24 Apr 2020 14:39:19 GMT

Hi,

I'd like to create a script that I could run in an assembly. The idea is that I'd select a part, click on a button in a form and - depending on the selected part - would import, constraints and adapt the part to my selection.

Now, I've done simple iLogic rules in the past where I could change my part depending on a measurement given in form. Is what I want to accomplish doable in a iLogic Rules or should I use the API ? What's the difference? Also, if using the API, can I script in Python or only in VB.net?

Thanks

-A

Re: Where to start? Inventor iLogic vs API

WCrihfield — Fri, 24 Apr 2020 16:58:58 GMT

Can you clarify more specifically what you want to happen when you click the button on the form?

As far as which coding environment to use. iLogic is an Add-in for Inventor, which has a DLL file, and can understand VB.NET language. It has several built-in advantages, but is fully contained within Inventor, after Inventor is started. Macro's are written in VBA, which is generally written using the VBA Editor. It obviously uses VBA (Visual Basic for Applications), this same platform is also used to access Microsoft Office products API.

Using iLogic is easier to set up Event Triggers for certain events. They can both access each other to a certain extent.

Using VBA is often a bit more clunky feeling, but has its own set of advantages. You can use a variety of code languages though. VBA likely has much more available documentation, that Inventor's iLogic does. But if you prefer VB.NET, there is a ton of documentation available for that too. It's all in personal preference.

topic Re: Where to start? Inventor iLogic vs API in Inventor Programming Forum

Where to start? Inventor iLogic vs API

Re: Where to start? Inventor iLogic vs API