iLogic replace from folders

[Anonymous]

I have 30 families of seals (arf arf!)

I would like to put family A in folder A

I would like to put family B in folder B

etc

During testing I had 10 seals in one folder & used :

Component.Replace("Part1:1", "OtherPartfilename.ipt", True)

But splitting the parts up into different folders breaks the model because (I'm guessing) the part can't be found.

My thought was to have one folder (Seals) with subfolder (Seal A, Seal B,etc) - is there a way to search the sub folders & use replace?

If I stick with one folder it will end up containing 300+ parts which will look messy.

Thanks

MES

[Anonymous]

Mark,

You are exactly right, ilogic will only search in the same folder(as the original component) for the replacement component. I came across this a couple of years ago when trying to replace library components with non library components.

Sorry to say that I (or the autodesk support guy) never found a solution to this other than having all of the components in the same folder. Not sure what you call a large group of seals, maybe a school or shoal? 🙂

[Curtis_W]

Hi MarkESmith,

You can find an example at this link where I replace components from different folders:

http://inventortrenches.blogspot.com/2011/08/ilogic-replace-revision-level-component.html

This example doesn't look like an exact fit for your challenge but hopefully it might give you some ideas.

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[xiaodong_liang]

Hi Curtis_Waguespack,

I went through your code. It looks good, but it seems to ask the user to input the new file name, instead of finding the new file automatically, which I think is what MarkESmith was looking for.

It is obviously to me that the existing functions of iLogic are not enough for the requirement. I would suggest the code could look for the assembly folder and tranvers the sub folders until the 'new' file is found, finally do replace as what your code demoed. Of course, the searching is a pure question of .NET API. I believe  MarkESmith could borrow some codes of yours. 🙂