Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
WCrihfield
in reply to: J-Camper

Hi @J-Camper.  As you may know, I am also a self-taught programmer (other than CNC stuff), but I have created several relatively basic Classes before, when needed.  I believe the two main starting points would be the Inherits statement, and/or the Implements statement.  The Inherits statement is probably more what you are looking for though (Inheritance Basics ).  Objects in Inventor's API (and iLogic API) can be a bit odd, because it seems like most of them are actually an Interface type object, instead of an instance of a Class (Link, Link, Link).  The PartDocument is an Interface, which is derived from the Document which is also an Interface.  You may not see this in the online help documentation, but you can see it by typing in these Types in an iLogic rule window, and looking at the Intellisense tips about those Types.  The Implements statement is more for, if you already have an Interface containing most of the skeleton of what you want, this is a way of insisting that this new Type contains all the skeletal aspects of that Interface, but then you must include the code defining all that stuff within your new Type.  The Inherits path seems simpler...no need to include code for all the same stuff that was in the parent Type, at least I do not think so, for the most part.  But I believe you can expand upon them, if you wanted to.

Wesley Crihfield

EESignature

(Not an Autodesk Employee)