"Copy to library" versus "Remove device"

"eSilviu" <silviu.epure@ugal.ro> wrote in message

news:iqls53$f6b$1@cheetah.cadsoft.de...

1. Supposing that I need only 1 footprint for LEDs only project;

2. Supposing that I have used the function "Copy to library" to copy LED

component from default library to my library;

3. Supposing that I can live with the fact that I had no choise to choose

what footprint to be copied, and all XXX footprints flooded my "project's

library";

4. Now: supposing that I go in my library and delete the "LED" device,...

guess what?!:

All the footprints that flooded my library (and I had never need of any of

them) remained in my library.

I guess I could remove them one by one, writing on paper the name of each

of one, and then writing by hand that names on the "Remove package" text

box. (PS: and hear the annoiyng beep sound for every footprint removal -

but this is an other thread...). Or I could create a new library right

from scratch... it will be faster...

 

Conclusion: We need a better way to handle components and footprints

between libraries! It s***s in may way as it is now.

>>>>>>>>>>>>>>>>>>>>>>>>>

Arrr. Library editing is CLUNKY at best.

But there is a way you can expedite (cough cough) the eradication of

undesired library components:

Suppose you have package called RES_0805 that you want rid of. Go into the

package editor for that footprint.

Type 'ren'

It's gone. Light speed it's not, but it works.

On 5/16/2011 2:32 PM, Brett Holden wrote:

"eSilviu"<silviu.epure@ugal.ro>  wrote in message

news:iqls53$f6b$1@cheetah.cadsoft.de...

>> 1. Supposing that I need only 1 footprint for LEDs only project;

>> 2. Supposing that I have used the function "Copy to library" to copy LED

>> component from default library to my library;

>> 3. Supposing that I can live with the fact that I had no choise to choose

>> what footprint to be copied, and all XXX footprints flooded my "project's

>> library";

>> 4. Now: supposing that I go in my library and delete the "LED" device,...

>> guess what?!:

>> All the footprints that flooded my library (and I had never need of any of

>> them) remained in my library.

>> I guess I could remove them one by one, writing on paper the name of each

>> of one, and then writing by hand that names on the "Remove package" text

>> box. (PS: and hear the annoiyng beep sound for every footprint removal -

>> but this is an other thread...). Or I could create a new library right

>> from scratch... it will be faster...

>>

>> Conclusion: We need a better way to handle components and footprints

>> between libraries! It s***s in may way as it is now.

>>>>>>>>>>>>>>>>>>>>>>>>>>

>

Arrr. Library editing is CLUNKY at best.

But there is a way you can expedite (cough cough) the eradication of

undesired library components:

 

Suppose you have package called RES_0805 that you want rid of. Go into the

package editor for that footprint.

Type 'ren'<enter>.

You are asked what the new name is. I like something short. 'X', for

instance.

type 'x'<enter>

type 'rem x'<enter>

 

It's gone. Light speed it's not, but it works.

 

>

nice trick

eSilviu wrote:

1. Supposing that I need only 1 footprint for LEDs only project;

2. Supposing that I have used the function "Copy to library" to copy

LED component from default library to my library;

3. Supposing that I can live with the fact that I had no choise to

choose what footprint to be copied, and all XXX footprints flooded my

"project's library";

4. Now: supposing that I go in my library and delete the "LED"

device,... guess what?!:

All the footprints that flooded my library (and I had never need of

any of them) remained in my library.

I guess I could remove them one by one, writing on paper the name of

each of one, and then writing by hand that names on the "Remove

package" text box. (PS: and hear the annoiyng beep sound for every

footprint removal - but this is an other thread...). Or I could

create a new library right from scratch... it will be faster...

 

Conclusion: We need a better way to handle components and footprints

between libraries! It s***s in may way as it is now.

I agree that additional flexibilty is needed when copying devices. It would

be good if you could select variant/s as you would then not get all the

packages of the other variants.

As a possible assist for the LED example given, you could run

del-pack-sym.ulp

That would get rid of all the unwanted packages once the LED device was

deleted. The down side is that if you have other packages that are unused

but you want to keep you will have to remove them from the script list

first.

Try it and see if it works for you.

Warren

"Warren Brayshaw" <warrenbrayshaw@paradise.net.nz> wrote in message

news:iqsikl$3gh$1@cheetah.cadsoft.de...

Try it and see if it works for you.

Thank you for suggestion.

It was faster to create a new library, to copy all needed components from

the old one and to rename-it as the old one.