For those who are interested. In my latest blog post, I share how to set up a "Virtual Component LIbrary" using an assembly file and a small iLogic rule.
http://www.hjalte.nl/97-virtual-component-library
Jelte de Jong
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Blog: hjalte.nl - github.com
coincidently, i had started a project some time ago that was very similar to this as i use VC's a lot as place holders and quantifiers. My version doesnt have an assembly parent, its run out of a json dataset instead. I can create and categorize my VC's in a table with all of the iProperties available. I call the tool, search for the one i want and add to my assembly with a button click. If one already exists, it adds another occurrence. I can also update my iProperty values in the Library editor and then push those to the VC in the model.
I'll see about making it into an addin, i have a bit going on atm so i'll try and push it for before Christmas
Nacho
Automation & Design Engineer
Inventor automation Programmer (C#, VB.Net / iLogic)
Furniture, Sheet Metal, Structural, Metal fab, Tradeshow, Fabrication, CNC
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Probably it can be done in much more elegant way's. Especially if you create an addin. But for my blog I wanted to keep it simple to make it simpler for users to use it. I expect that creating a json file is a bridge to far for most mechanical engineers. And creating tools to create the json file is not something that you should do in iLogic but in an addin. So the blog is a bit of a compromise. 😊
Jelte de Jong
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Blog: hjalte.nl - github.com
