- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have attached two of my 'standalone' (contain all required code) external rules that create a Windows Form, then show it, then react to its events. The one named WinForm In Rule Example 1 is an older one that I created primarily for learning purposes / practice, and to show how to react to various events of popular controls in a Windows Form. It does not really interact with any specific Inventor Document. The other one is also not necessarily for a specific document either, but was a utility for the task of ensuring that specific properties were present, and set to a specific value, in all Inventor files of the specified type in a folder. It is not necessarily the most efficient way to do things, and is certainly pretty difficult initially to do it this way, but gives us more control than what we have with simple iLogic forms, depending on our needs and the situation.
It would have likely been easier to use Visual Studio to design the form, then somehow transfer the required code over into an external iLogic rule, or create a DLL file, and put it into the proper location, so that we could reference it from an iLogic rule, one way or another. But, even though I do have VS2022 Community installed, and the Inventor SDK stuff installed, I don't think VS is set-up properly or something like that. I have to rely on our 'corporate' IT dept to do all installations and anything requiring administrative rights, since no one in our entire corporation is allowed to have admin rights on their own computers. This is what has prevented me from being able to create my own add-ins and/or exe's. I do not have a degree in software development, so I was not sure what all 'packages' or whatever needed to be downloaded and set-up in it when they installed it.
Wesley Crihfield
(Not an Autodesk Employee)