Commonly Used Parts (ipt) - Content Centre, Library & Local User Gen Copies

[arkelec]

Looking for some pointers on the best way to store commonly used parts.

Additionally, how to deal with an iPart with user input variable (length) that generates a unique file every time it's placed in an assembly.

So, firstly, the common files.

At present, I have the Project files stored in sub-folders within the main folder "Project".  I have another main folder "Libraries",  which has sub-folders for various commonly used components.  The actual library & content centre files are in the default locations (i.e. %user etc)

For the project structure, I list "Libraries" under "Workgroup Search Paths".

If I need to link to another project folder as there are some parts I need to use, I also add it to "Workgroup Search Paths".

I often need to create a part that will become a "library" part whilst working on any given project so don't like the "this location is outside of the working part" malarkey.

Is the above good working practice, or is there a better way?

Secondly, the iParts with variable lengths.

Is there any way to have the multitude of files generated when explicit lengths are created within an assembly stored in one central place?

I saw on another thread there might be a way to do this, but it uses libraries & I've no experience in adding iPart files to libraries.

[johnsonshiue]

Hi! I think you are setting things up the way I would do. Regarding iPart with varying parameter, it is called custom iPart members. To create a custom iPart member, you will need to have a custom iPart factory first. It is pretty straight forward to do. Open an existing iPart factory and right-click on any configurable column -> check Custom Parameter Column. Then the iPart factory becomes custom. You will not be able to generate member files within the factory. You will need to place the iPart factory into an assembly and you will get prompted to enter a value for the custom parameter. Custom iPart members are like derived parts with a table. They are still driven by the table for non-custom columns but you can easily override the custom parameter value.

Many thanks!

[arkelec]

Thanks @johnsonshiue for the reply.

I know about the iPart custom parameter, my question was more to do with where the generated iPart files are stored after the custom parameter is entered.

I'm guessing that there is no way to locate these files in a central location.

[johnsonshiue]

Hi! The custom ipart member files should be stored in the same folder as the ipart factory. Otherwise, the link between the member file and the factory file will be lost temporarily.

Many thanks!

[arkelec]

OK, but apparently by default, they are not. The are stored in the Workspace root folder.

I "want" them to be stored where the iPart file is stored, but they are not. Just to be clear - this iPart has a Custom parameter for length.

[johnsonshiue]

Hi!  I am sorry I think I am confused. Do you mind sharing an example exhibiting the problem here? Please use Pack and Go to include all the files and the project structure and the project file.

Many thanks!