How to add existing component from PUBLIC LIBRARY to OWN Library.io (so I can modify it)

How to add existing component from PUBLIC LIBRARY to OWN Library.io (so I can modify it)

infoledeco_sk
Participant Participant
384 Views
4 Replies
Message 1 of 5

How to add existing component from PUBLIC LIBRARY to OWN Library.io (so I can modify it)

infoledeco_sk
Participant
Participant

I spent several hours to find (no luck so far) a way how to add component with all the footprints, 3D model, schematic, I have found in public library.io to import it to MY OWN library.io private library, so I could do some changes (rename it, add some Order codes, add 3D model etc)
example I found SHK20L even it is without 3D model, URL here : https://library.io/packages/14071-SHK20L
And want it to become a component in my OWN Library.io managed library....I can not see any import /export options, any upload, anything in the source library, nor in destination library (destination library has under " create new component " a Import function, but it opens a Dialog window again with all my own Library.io managed libraries, and no "Upload from local PC" or browse other libraries, etc is available. the same thing from other side : when I find a component in whatever library, there are no options to "COPY IT TO MY OWN LIBRARY.IO) .....in Eagle it used to be very un-friendly, but in Fusion have set new benchmark for me....basic features become super user unfriendly

0 Likes
385 Views
4 Replies
Replies (4)
Message 2 of 5

Evert_2N3055
Advocate
Advocate

It's not that difficult if you know how to 😉

 

In de library manager look for the lib you want to copy from, enable this library

Open your personal library press add component and then import, browse to the lib you want to copy from, select the required component and done.

 

CopyParts.gif

 

 

0 Likes
Message 3 of 5

infoledeco_sk
Participant
Participant

Thanks, worked.
....so I have to always find component I like, Enable library, do import, then disable the library again....
I would suggest better workflow : allow to import from any library, if enabled or not...
Or even better :
If I browse libraries, and will find component I like : Right Click -> Add to my Library -> Choose library -> Save with automatic PUSH to the library.io cloud.....keeping the workflow in standard way through UI on all devices/software will lead to easier user navigation and work....so ANY user can just work and discover new features in standard way a not to search "how to" for every single feature on Autodesk forum, youtube tutorials etc....
Tinny messup with libraries/versions I can not get used to it : According to your tutorial I end up with 2 same libraries enabled if I like it or not. 
I have enabled 1 new library to copy part from + only my library.io libraries> I open Library.io library -> Add component-> pick component from source library -> Click Save -> Click push to library.io (which is totally nonsense to me) to have it on cloud if I need to use same device on other PC (why it can not happend automatically?...like everything in cloud? cloud=single cloud space). So if I do all that, automatically ANOTHER LOCAL MANAGED library is TURNED ON (confusing, have to disable it again) + my Library.io seems to have "new version: and I have to download the update again....why why?The library management is very unclear (if you work 10 years in the cloud, having local changes, which need to push all the time to cloud, update, and re-update, is very strange + all the time the libraries you turn off do turn on because whatever reason...it is far from "cloud concepts"...cant understand why If I open cloud library and modify it, change is saved locally and need to sync it again, then resync it, and turn of AGAIN local library which did turn on automatically....so frustrating, sorry....even Eagle was sometimes frustrating, but this is new level for me.

0 Likes
Message 4 of 5

jorge_garcia
Autodesk
Autodesk

Hi @infoledeco_sk,

 

We are working to improve this. Right now you have two cloud infrastructures, one for library.io and one for Fusion Team. The eventual goal is to get it down to just 1 infrastructure for 90% of use cases so that the only time you would need to use library.io would be for crossing hubs.

 

BTW, you don't have to turn a source library off if you don't want to. As long as the source lib has a different name than the one you are copying to, there should be no confusion. Things get confusing when you have multiple libs with the same name on different infrastructure. We are working to remedy this.

 

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

 

Best Regards,



Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes
Message 5 of 5

infoledeco_sk
Participant
Participant

Hi, glad some changes are to be expected, hopefully it will take no longer than few years ( as most improovements are either not done at all or takes incredibly long time) I am looking forward one day to feel the work in Fusion like in real cloud enviroment (which should not be hard if it is done right, Google had its Gdrive and Sheets over 10 years ago fully cloud based 🙂 

0 Likes