re: Bug? Library parts silently auto connecting (dated 6-20)

That sounds simple, thank you. I guess now I have one less reason not to

upgrade (again). Eagle gave me extreme heartburn with the bugs in early v6.

I reverted back and have been in no hurry to jump again despite promised

imprevements.

"Chuck Huber" <chuck.huber@dukepro.com> wrote in message

news:jseua6$h3s$1@cheetah.cadsoft.de...

Aren't the libraries maintained in XML now?

 

So why not just use a plain text editor like vim or notepad and do a

global search and replace in the library file?

 

Try replacing

   direction="sup"

with

   direction="pas"

 

Make a backup first, of course.

 

Enjoy,

   - Chuck

 

>

 

On 06/26/2012 10:57 PM, Brett Holden wrote:

>> I appologize for going off. If my request is too difficult without

>> resorting

>> to Linux or an Linux emulator (or whatever), then that's just tough

>> nuggies

>> for me. Maybe also for however untold numbers of persons who

>> inadvertently

>> created libraries using Pwr pins that will get connected automatically,

>> to

>> untold dismay. But I'll just speak for myself. The most expeditious way

>> to

>> correct the conundrum may be going through each library one-by one. No

>> big

>> deal, I'm used to bigger trouble than that.

>>

>> A note to CadSoft. So, that's the way you've done it for 20 years?

>> I suppose if It was good enough for my daddy then it should be good

>> enough

>> for me, eh?

>> You can call anything you want a non issue and simply ignore it.  Sure,

>> Eagle is "EASY" as in "Easily Applicable". Really? Maybe if you're a

>> programmer.

>>

>> -

>>

>> "Robert Pearce" <news@bdt-home.demon.co.uk> wrote in message

>> news:bWYIrHNOo45PFwMN@daniel.huneausware.local...

>>> On Sat, 23 Jun 2012, Olin Lathrop wrote to us saying :

>>>> Robert Pearce wrote on Fri, 22 June 2012 18:57

>>>>> What do you mean, you don't know what SED is? Honestly, what sort of

>>>>> garbage OS are you using? Oh, I see, Windoze. Well.... there is the

>>>>> GnuWin package to repair that problem.

>>>>

>>>> The garbage I see here is expecting a user of one operating system to

>>>> know

>>>> commands of another, a religious diatribe masquerading as a helpful

>>>> answer,

>>>> and your proposed method of changing power pins.

>>>>

>>> Nothing religious about it. Windows lacks any useful tools, but I

>>> offered

>>> a solution to that.

>>>

>>>> Your method basically creates a whole new library, which then no longer

>>>> has

>>>> association to the various projects that uses it.

>>>

>>> Unless it has the same name, in which case Eagle's method of associating

>>> libraries can easily be made to find it.

>>>

>>>> A better way would be to

>>>> write a ULP to scan a library for power pins, write the Eagle commands

>>>> to

>>>> change them to whatever you like, then run those commands on exit from

>>>> the

>>>> ULP.

>>>

>>> Which I note you have not done, because it's not nearly as easy as my

>>> approach.

>>>

>>>>  This has the advantage of editing the library in place.

>>>

>>> That's not an advantage because you don't really want to go hacking all

>>> your libraries "in place" and then find you've messed up. FAR better to

>>> create new ones, check they work, and then either copy them over the

>>> originals or BETTER STILL use the custom ones from now on leaving the

>>> originals still available should you ever choose to go back.

>>>

>>> You and Brett may choose to see my genuinely offered help as a personal

>>> attack or a religious diatribe. If so, you are the only ones who lose

>>> out.

>>> --

>>> Rob Pearce                       http://www.bdt-home.demon.co.uk

>>>

>>> The contents of     | All power corrupts, but we need electricity.

>>> this message are    |

>>> purely my opinion.  |

>>> Don't believe a     |

>>> word.               |

>>

>>

On 6/27/2012 8:31 AM, Chuck Huber wrote:

On 06/27/2012 08:28 AM, Chuck Huber wrote:

>> Aren't the libraries maintained in XML now?

>>

>> So why not just use a plain text editor like vim or notepad and do a

>> global search and replace in the library file?

>>

>> Try replacing

>>      direction="sup"

>> with

>>      direction="pas"

 

Or replace

     direction="pwr"

with

     direction="pas"

 

     - Chuck

 

Hi Chuck,

You're the man, I like how you can quietly swoop in, provide an easy

solution without getting involved in the Linux vs Windows war.

Good job.

Best Regards,

Jorge Garcia

Cadsoft Support

Am 27.06.2012 14:31, schrieb Chuck Huber:

On 06/27/2012 08:28 AM, Chuck Huber wrote:

>> Aren't the libraries maintained in XML now?

>>

>> So why not just use a plain text editor like vim or notepad and do a

>> global search and replace in the library file?

>>

>> Try replacing

>>      direction="sup"

>> with

>>      direction="pas"

 

Or replace

     direction="pwr"

with

     direction="pas"

 

     - Chuck

 

That is too easy chuck

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

On 06/27/2012 08:28 AM, Chuck Huber wrote:

Aren't the libraries maintained in XML now?

 

So why not just use a plain text editor like vim or notepad and do a

global search and replace in the library file?

 

Try replacing

    direction="sup"

with

    direction="pas"

Or replace

    direction="pwr"

with

    direction="pas"

    - Chuck

Aren't the libraries maintained in XML now?

So why not just use a plain text editor like vim or notepad and do a

global search and replace in the library file?

Try replacing

    direction="sup"

with

    direction="pas"

Make a backup first, of course.

Enjoy,

    - Chuck

On 06/26/2012 10:57 PM, Brett Holden wrote:

I appologize for going off. If my request is too difficult without resorting

to Linux or an Linux emulator (or whatever), then that's just tough nuggies

for me. Maybe also for however untold numbers of persons who inadvertently

created libraries using Pwr pins that will get connected automatically, to

untold dismay. But I'll just speak for myself. The most expeditious way to

correct the conundrum may be going through each library one-by one. No big

deal, I'm used to bigger trouble than that.

 

A note to CadSoft. So, that's the way you've done it for 20 years?

I suppose if It was good enough for my daddy then it should be good enough

for me, eh?

You can call anything you want a non issue and simply ignore it.  Sure,

Eagle is "EASY" as in "Easily Applicable". Really? Maybe if you're a

programmer.

 

--------------------------------------

 

"Robert Pearce" <news@bdt-home.demon.co.uk> wrote in message

news:bWYIrHNOo45PFwMN@daniel.huneausware.local...

>> On Sat, 23 Jun 2012, Olin Lathrop wrote to us saying :

>>> Robert Pearce wrote on Fri, 22 June 2012 18:57

>>>> What do you mean, you don't know what SED is? Honestly, what sort of

>>>> garbage OS are you using? Oh, I see, Windoze. Well.... there is the

>>>> GnuWin package to repair that problem.

>>>

>>> The garbage I see here is expecting a user of one operating system to know

>>> commands of another, a religious diatribe masquerading as a helpful

>>> answer,

>>> and your proposed method of changing power pins.

>>>

>> Nothing religious about it. Windows lacks any useful tools, but I offered

>> a solution to that.

>>

>>> Your method basically creates a whole new library, which then no longer

>>> has

>>> association to the various projects that uses it.

>>

>> Unless it has the same name, in which case Eagle's method of associating

>> libraries can easily be made to find it.

>>

>>> A better way would be to

>>> write a ULP to scan a library for power pins, write the Eagle commands to

>>> change them to whatever you like, then run those commands on exit from the

>>> ULP.

>>

>> Which I note you have not done, because it's not nearly as easy as my

>> approach.

>>

>>>  This has the advantage of editing the library in place.

>>

>> That's not an advantage because you don't really want to go hacking all

>> your libraries "in place" and then find you've messed up. FAR better to

>> create new ones, check they work, and then either copy them over the

>> originals or BETTER STILL use the custom ones from now on leaving the

>> originals still available should you ever choose to go back.

>>

>> You and Brett may choose to see my genuinely offered help as a personal

>> attack or a religious diatribe. If so, you are the only ones who lose out.

>> --

>> Rob Pearce                       http://www.bdt-home.demon.co.uk

>>

>> The contents of     | All power corrupts, but we need electricity.

>> this message are    |

>> purely my opinion.  |

>> Don't believe a     |

>> word.               |

I appologize for going off. If my request is too difficult without resorting

to Linux or an Linux emulator (or whatever), then that's just tough nuggies

for me. Maybe also for however untold numbers of persons who inadvertently

created libraries using Pwr pins that will get connected automatically, to

untold dismay. But I'll just speak for myself. The most expeditious way to

correct the conundrum may be going through each library one-by one. No big

deal, I'm used to bigger trouble than that.

A note to CadSoft. So, that's the way you've done it for 20 years?

I suppose if It was good enough for my daddy then it should be good enough

for me, eh?

You can call anything you want a non issue and simply ignore it.  Sure,

Eagle is "EASY" as in "Easily Applicable". Really? Maybe if you're a

programmer.

-

"Robert Pearce" <news@bdt-home.demon.co.uk> wrote in message

news:bWYIrHNOo45PFwMN@daniel.huneausware.local...

On Sat, 23 Jun 2012, Olin Lathrop wrote to us saying :

>>Robert Pearce wrote on Fri, 22 June 2012 18:57

>>> What do you mean, you don't know what SED is? Honestly, what sort of

>>> garbage OS are you using? Oh, I see, Windoze. Well.... there is the

>>> GnuWin package to repair that problem.

>>

>>The garbage I see here is expecting a user of one operating system to know

>>commands of another, a religious diatribe masquerading as a helpful

>>answer,

>>and your proposed method of changing power pins.

>>

Nothing religious about it. Windows lacks any useful tools, but I offered

a solution to that.

 

>>Your method basically creates a whole new library, which then no longer

>>has

>>association to the various projects that uses it.

 

Unless it has the same name, in which case Eagle's method of associating

libraries can easily be made to find it.

 

>> A better way would be to

>>write a ULP to scan a library for power pins, write the Eagle commands to

>>change them to whatever you like, then run those commands on exit from the

>>ULP.

 

Which I note you have not done, because it's not nearly as easy as my

approach.

 

>>  This has the advantage of editing the library in place.

 

That's not an advantage because you don't really want to go hacking all

your libraries "in place" and then find you've messed up. FAR better to

create new ones, check they work, and then either copy them over the

originals or BETTER STILL use the custom ones from now on leaving the

originals still available should you ever choose to go back.

 

You and Brett may choose to see my genuinely offered help as a personal

attack or a religious diatribe. If so, you are the only ones who lose out.

--

Rob Pearce                       http://www.bdt-home.demon.co.uk

 

The contents of     | All power corrupts, but we need electricity.

this message are    |

purely my opinion.  |

Don't believe a     |

word.               |

On Sat, 23 Jun 2012, Olin Lathrop wrote to us saying :

>Robert Pearce wrote on Fri, 22 June 2012 18:57

>> What do you mean, you don't know what SED is? Honestly, what sort of

>> garbage OS are you using? Oh, I see, Windoze. Well.... there is the

>> GnuWin package to repair that problem.

>The garbage I see here is expecting a user of one operating system to know

>commands of another, a religious diatribe masquerading as a helpful answer,

>and your proposed method of changing power pins.

Nothing religious about it. Windows lacks any useful tools, but I

offered a solution to that.

>Your method basically creates a whole new library, which then no longer has

>association to the various projects that uses it.

Unless it has the same name, in which case Eagle's method of associating

libraries can easily be made to find it.

A better way would be to

>write a ULP to scan a library for power pins, write the Eagle commands to

>change them to whatever you like, then run those commands on exit from the

>ULP.

Which I note you have not done, because it's not nearly as easy as my

approach.

This has the advantage of editing the library in place.

That's not an advantage because you don't really want to go hacking all

your libraries "in place" and then find you've messed up. FAR better to

create new ones, check they work, and then either copy them over the

originals or BETTER STILL use the custom ones from now on leaving the

originals still available should you ever choose to go back.

You and Brett may choose to see my genuinely offered help as a personal

attack or a religious diatribe. If so, you are the only ones who lose

out.

--

Rob Pearce                       http://www.bdt-home.demon.co.uk

The contents of     | All power corrupts, but we need electricity.

this message are    |

purely my opinion.  |

Don't believe a     |

word.               |

Robert Pearce wrote on Fri, 22 June 2012 18:57

What do you mean, you don't know what SED is? Honestly, what sort of

garbage OS are you using? Oh, I see, Windoze. Well.... there is the

GnuWin package to repair that problem.

The garbage I see here is expecting a user of one operating system to know

commands of another, a religious diatribe masquerading as a helpful answer,

and your proposed method of changing power pins.

Your method basically creates a whole new library, which then no longer has

association to the various projects that uses it.  A better way would be to

write a ULP to scan a library for power pins, write the Eagle commands to

change them to whatever you like, then run those commands on exit from the

ULP.  This has the advantage of editing the library in place.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

On Thu, 21 Jun 2012, Brett Holden wrote to us saying :

>Does anybody have a script or ULP handy to search the various libraries and

>change any pins with direction Pwr, to some other direction? (Of course,

>SUPPLY libraries must be hidden by user, or somehow skipped!)

Assuming you want to change ALL the power pins in a given library (so

you won't do this with the supply.lbr for example) then:

1) Export the library as a script (from the library editor File menu)

2) Run "sed -i s/Pwr/Pas/g" or similar on that script

3) Create a new library and import that modified script

4) Save the resulting library in your "custom" directory

You may need to tweak that sed command a fraction, but that's the

essence of it.

What do you mean, you don't know what SED is? Honestly, what sort of

garbage OS are you using? Oh, I see, Windoze. Well.... there is the

GnuWin package to repair that problem.

--

Rob Pearce                       http://www.bdt-home.demon.co.uk

The contents of     | All power corrupts, but we need electricity.

this message are    |

purely my opinion.  |

Don't believe a     |

word.               |