Hello,
I am trying to make my first addin. My addin will open an assembly model that has a form in it. This form is what drives all of the changes to the assy. The assembly changes size and shape, then it will "saveas" itself and all parts and sub assemblies. My trouble is how to address the form, whether to keep it in inventor or recreate it in visual studio.
If I keep the form in inventor:
If I recreate the form in visual studio:
What do you think?
Could you show what you mean with some sketches or screenshots etc.
Regards,
Arthur Knoors
Autodesk Affiliations:
Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:Drawing List!|Toggle Drawing Sheet!|Workplane Resize!|Drawing View Locker!|Multi Sheet to Mono Sheet!|Drawing Weld Symbols!|Drawing View Label Align!|Open From Balloon!|Model State Lock!
Posts and Ideas:Dimension Component!|Partlist Export!|Derive I-properties!|Vault Prompts Via API!|Vault Handbook/Manual!|Drawing Toggle Sheets!|Vault Defer Update!
! For administrative reasons, please mark a "Solution as solved" when the issue is solved !
Although iLogic forms are the easiest and simplest to create, they have the lease amount of tools available for their creation and functionality. And they are the least interactive, when compared to the alternatives. VBA UserForm's are a step up from the iLogic form. Not only do you have tools available to help you create the visible aspects of the form, but you also have the ability to include a UserForm Module, which is a collection of code intended to set all the specifications of the form, its contents/source data, and how you want it to react to user interaction with it. Then there is the direct Windows.Forms.Form, which can be fully created, set-up, shown, and used, entirely by a single block of vb.net code, if needed.
A while back, I created a contribution post, in which I demonstrate how you can completely create and use a fairly simple Windows form, from scratch, launch it, and provide feedback to your user interactions with it, all from a single iLogic rule (because iLogic uses vb.net). Here is the link to it, in case it may provide you with some ideas on how to coordinate your project.
If this solved your problem, or answered your question, please click ACCEPT SOLUTION.
Or, if this helped you, please click (LIKE or KUDOS) 👍.
If you have time, please... Vote For My IDEAS :light_bulb:or you can Explore My CONTRIBUTIONS
Inventor 2021 Help | Inventor Forum | Inventor Customization Forum | Inventor Ideas Forum
Wesley Crihfield
(Not an Autodesk Employee)
NICE! I wouldn't have thought to make a windows form in iLogic. That helps narrow my decision down to keeping the form in the model. I just have one question. How do I access that form from the addin?
I might not be able to help much there. The place I'm working doesn't allow anyone to have 'administrator's rights' to on their own computers, so I'm not currently able to create or install add-ins. However, know there are ways to deal with this situation. One thing you could do is simply include the code for the Windows form somewhere within your add-in's code/resources. Another option is to sort of 'capture' the form when it gets launched, but this method may only give you the ability to interact with it, rather than the ability to change its design or functionality.
Wesley Crihfield
(Not an Autodesk Employee)
Can't find what you're looking for? Ask the community or share your knowledge.