This is a follow-up of my tutorial: ”Creating an Inventor addin”. In one of the chapters I wrote how to add a button to your addin. But I left out how to add an icon to that button. Because it need some explanation and I did find the tutorial already quite long.

This is a follow-up of my tutorial: "Creating an Inventor Addin". Writing code usually involves a lot of testing. In the case of writing addins this can become a pain. Each time you want to test your addon you need to restart Inventor and maybe open a document.

This is a follow-up on my tutorials on creating an addin. In the 1e part, we created an addin that searches all iLogic rules. We used an inputbox to get input from the user. We used notepad to show the results to the user. We can do this in a more elegant way by creating a custom form (window). 

Every once and a while someone comes to the forum with the same problem: "My addin will not load." Figuring out what the problem is without the code is hard. But this is the checklist that I use to figure out what the problem is. 

In the post "Adding a form to your addin." we created a simple form/window. But there are problems with those windows. They are never a part of Inventor and therefore always in the way of your Inventor screen or the other way around. (They are in front or at the back of your Inventor Window.) A dockable window can help in those situations.

Brian Ekins wrote a great article on this topic. You can find it here:
https://modthemachine.typepad.com/my_weblog/2015/09/improving-your-programs-performance.html
I’m not going to repeat his article here. But I found a couple of other ways to optimize my code.

I maintain some add-ins and some tools. Most of those addins and tools deal with parameters and iProperties.  I have been putting it for a long time but lately, I have been updating these tools to work with model states.  In this post, I want to share some key learnings. I found that there are some things that you always need to consider when working with model data (like parameters and iProperies) in combination with model states.