On Feb 18, 2008 2:48 AM, Harvey White <
madyn@...> wrote:
>
> Actually, and in an odd sense, it does.
>
> If you go into the library of that part, and change the pad diameter,
> then save the library, do a library update, then it does.
>
> That's for all instances of that part, though.
Yes, but that's hardly changing it in the layout ;-)
Sometimes it makes sense to change one or a few pads like in a special
area, where there is not enough space. You don't want to change all
parts, even in the same layout. With eagle this is a royal pain, with
other software this is easy.
>
> If you want to preserve your own libraries, then you must copy a part
> from the supplied libraries to your own, change that part, and then
> replace that part (every instance) with your own part. Then you have
> control over it regardless of what you (or they) do with the eagle
> libraries.
That's what i do anyway.
> Royal pain, but only needs to be done once.
And every time you want to change any tiny thing.
It's surprising really that they even allow us to move the text
(component reference and value). We ought to change that in the
library too ;-)
> Oh, and you might look at the design rules and change them. Doing so
> can change the size of a pad for a via, for instance, globally. Never
> tried it with parts, though.
I know, another peculiarity. But even if it does work for parts (which
i don't know) it would still be useless to have one minimum size when
i need smaller and larger pads.
Worst software ever made that eagle, well, close to anyway.
ST