Interrogating the Open Document in Inventor VBA Environment Now of course can go into the model browser and find it, but what if you want to access it programmatically, where does it live in the structure of the model document? Watch the video below to see how to get this information quickly. Let’s say, for example, you’re looking for the “Work Point” object that represents the origin of a particular part. By using the little trick below however, you can see the API objects in a live document, populated with real data, which makes it a lot easier to understand. The API documentation for Inventor, while thorough, is pretty dry to read and can be difficult to navigate if you’re unfamiliar with it. To find out more where these objects are stored, and how they interact with other objects, you need a reference. For example, if I’m building a tool to ensure that the designer fills out all the appropriate metadata for a model, I know straight away, that I’ll be working a lot with iProperties. With a limited mental picture of how the finished tool may look, often the only thing I know at the start, is the rough area of Inventor I’ll be working with. Usually when I start working on a customisation job, I only have a rough idea of what I want to achieve. Writing pseudo code to figure out the ‘flow’ of your program.Interrogating a live document to learn from and capture information.I’m going to split this up into a couple of categories: If there is enough interest, I could do a similar article on the Vault equivalent. Having said that, there are definitely a couple of tips and tricks I can share which should help novice coders get started with customising Autodesk Inventor. The truth is, unless I’m working on a commercial project that has been carefully scoped, budgeted and scheduled, most of the time I just ‘hack’ something together. In his words, he suffers from “the worst kind of writers’ block.” I totally sympathise with this issue as I have the same problem myself, quite frequently. He already has a pretty good handle on code structure and syntax, but struggles to know where to start in actually bringing his idea to life. Recently, a friend (and colleague) asked me how I go about planning the development of a new application or customisation project.
0 kommentar(er)
