Editing package in linked teams library enforces importing the package again (separately to already imported library)

[dev2EP8UX]

Hello, 

I have a linked teams library open (the library has been saved). Trying to edit the package of one of the components...

leads to:

Q1) Why does the package need to be imported again when the library it's in is already a teams library?

If I click Import, a Save dialog pops up that forces me to save the package separately from the library:

Q2) I would like to edit components/footprints/packages inside the library they belong to, without having to work with components or whatever as separate files. How can that be done? 

Thanks in advance,

g

[jorge_garcia · Accepted solution]

Hello @dev2EP8UX,

I hope you're doing well. I'll answer your questions in order:

1) This is necessary because Teams and library.io are completely separate systems. Besides the library being stored on teams the 3D models are also stored as separate assets that the library links to.

2) I wish that too, it's currently not possible and it's because of the way 3D models are linked to a lib and not actually part of the lib. We are working on improving that but for now that's how it works.

To simplify this, I recommend creating a libraries project and then within it having a folder where you store the 3d models so they are out of the way.

Let me know if there is anything else I can do for you.

Best Regards,

[dev2EP8UX]

Jorge, Thank you. OK, so it is what it is then. The handling of editing/maintaining of existing libraries seems to have a lot of room for improvement regarding clarity, user friendliness, organisation and efficiency. At the moment, this is a convoluted mess of clicks and windows to achieve very simple things. 

Regards,

g