Correct workflow for a library of components?

[Anonymous]

I know that I can bring a component into another design as a linked component, but the component I'm adding must be in the same project as the design I'm working on.  Is there any way to link across projects?

I have a component called "LCD module" that I use in a bunch of different unrelated projects and I'd like to have one master version in a project called "Library" that everything else links to.  As far as I can tell, what I have to do instead is copy the LCD module design into each project that needs it then link it into the product design from there, so now I have a bunch of different copies of the LCD module running around and if I tweak something to improve it in one project, no other project gets the benefit of that new version.

Is there a better way to maintain a library of commonly-used components, or is Fusion 360 just a little weak in this area?

[daniel_lyall]

@Anonymous you right click on the object you won't in the model and select insert into current design 

[TrippyLighting]

You are correct that linking across projects is currently not possible in Fusion 360.

The question, however, is if that link really needs to be maintained.

If the LCD module is a of-the-shelf standard component that is not going to be changed, there is really no reason to keep it linked.

Even if it might get modified, you may still ask yourself if you want that modified component to be changed in existing designs. 

[Anonymous]

@daniel_lyall, what you described works fine for components in the same project as the design I'm working on.  It doesn't work for components that are in a different project; like, say, a project named Library that holds a bunch of commonly-used parts.  If I try to insert a component from a different project I get this:

[TrippyLighting]

You can still insert them by clicking on "Proceed", they just won't be linked.

[daniel_lyall]

yer that be a pain you can use what I showed if you don't want it linked if it is from another file location if it's from the same place it is linked, otherwise you have to open it and copy then past to keep link or past new to have no link.

this needs fixed it makes the file system a bit darft.

to make life easier with the way it is only have one file for everything what is daft as well.

I have a library of components as well they don't need linked as they are a solid model of a part what will never change so never ran into this with doing this.

so you might need to have 2 parts file one that parts don't need changed or never will be so it just insert into current model and another for copy and past.

I think when they finish the update of the file system this will be corrected, I am sure they fixed this in the update I will have to watch the vid again