Update Library does NOT update schematic or board

Am 18.05.2011 03:00, schrieb Marvin Dawson:

Update Library (specific) or Update All Libraries does not update

schematic or board with library changes.

The only work-around is to open the schematic and "pretend" to add the

revised component, acknowledge the "updated" messages, and then escape

(cancel) the addition.

This is unacceptable behavior.

Eagle should check for updated devices/packages whenever a board is

loaded and prompt for update or not. And, Update Library should WORK!!!

Are you sure that you are editing the same library as you are using

with the ADD command. Could there be two different versions of this

library?

--

Mit freundlichen Gruessen / Best regards

Richard Hammerl

  CadSoft Support -- hotline@cadsoft.de

  FAQ: http://www.cadsoft.de/faq.htm

Richard Hammerl wrote:

Am 18.05.2011 03:00, schrieb Marvin Dawson:

>> Update Library (specific) or Update All Libraries does not update

>> schematic or board with library changes.

>> The only work-around is to open the schematic and "pretend" to add the

>> revised component, acknowledge the "updated" messages, and then escape

>> (cancel) the addition.

>> This is unacceptable behavior.

>> Eagle should check for updated devices/packages whenever a board is

>> loaded and prompt for update or not. And, Update Library should WORK!!!

 

Are you sure that you are editing the same library as you are using

with the ADD command. Could there be two different versions of this

library?

 

Thanks, everyone for all the suggestions.

There was only one (network) copy of the shared library.

I believe that the problem was likely due to our naming the library with

an @ sign at the beginning.  This was done in order to move it up

towards the top of the library listings, making it easier to find.

However, appending the @ sign to the beginning appears to have caused

Eagle to not find or update the library.

UPDATE @library_name or UPDATE ALL was probably looking for

library_name, without the leading @ sign character.

We have renamed our library with a leading 0 (zero) to hopefully resolve

these problems.  Eagle should probably caution or not permit library

names that begin with @ character.

We have had similar problems when someone named a new device "NAME.DEV".

  Eagle appended .dev to it, resulting in "NAME.DEV.dev", and it was

nearly impossible to correct.

Richard Hammerl wrote:

Am 18.05.2011 03:00, schrieb Marvin Dawson:

>> Update Library (specific) or Update All Libraries does not update

>> schematic or board with library changes.

>> The only work-around is to open the schematic and "pretend" to add the

>> revised component, acknowledge the "updated" messages, and then escape

>> (cancel) the addition.

>> This is unacceptable behavior.

>> Eagle should check for updated devices/packages whenever a board is

>> loaded and prompt for update or not. And, Update Library should WORK!!!

 

Are you sure that you are editing the same library as you are using

with the ADD command. Could there be two different versions of this

library?

 

Thanks, everyone for all the suggestions.

There was only one (network) copy of the shared library.

I believe that the problem was likely due to our naming the library with

an @ sign at the beginning.  This was done in order to move it up

towards the top of the library listings, making it easier to find.

However, appending the @ sign to the beginning appears to have caused

Eagle to not find or update the library.

UPDATE @library_name or UPDATE ALL was probably looking for

library_name, without the leading @ sign character.

We have renamed our library with a leading 0 (zero) to hopefully resolve

these problems.  Eagle should probably caution or not permit library

names that begin with @ character.

We have had similar problems when someone named a new device "NAME.DEV".

  Eagle appended .dev to it, resulting in "NAME.DEV.dev", and it was

nearly impossible to correct.

Am 21.05.2011 19:18, schrieb Marvin Dawson:

Richard Hammerl wrote:

>> Am 18.05.2011 03:00, schrieb Marvin Dawson:

>>> Update Library (specific) or Update All Libraries does not update

>>> schematic or board with library changes.

>>> The only work-around is to open the schematic and "pretend" to add the

>>> revised component, acknowledge the "updated" messages, and then escape

>>> (cancel) the addition.

>>> This is unacceptable behavior.

>>> Eagle should check for updated devices/packages whenever a board is

>>> loaded and prompt for update or not. And, Update Library should WORK!!!

>>

>> Are you sure that you are editing the same library as you are using

>> with the ADD command. Could there be two different versions of this

>> library?

>>

Thanks, everyone for all the suggestions.

There was only one (network) copy of the shared library.

I believe that the problem was likely due to our naming the library with

an @ sign at the beginning. This was done in order to move it up towards

the top of the library listings, making it easier to find.

However, appending the @ sign to the beginning appears to have caused

Eagle to not find or update the library.

UPDATE @library_name or UPDATE ALL was probably looking for

library_name, without the leading @ sign character.

We have renamed our library with a leading 0 (zero) to hopefully resolve

these problems. Eagle should probably caution or not permit library

names that begin with @ character.

We have had similar problems when someone named a new device "NAME.DEV".

Eagle appended .dev to it, resulting in "NAME.DEV.dev", and it was

nearly impossible to correct.

The library names must exactly match otherwise UPDATE does not work.

In case you want to rename a device/package/symbol in a library you

can use, for example, EXPORT SCRIPT to write the whole library file

in a script file. Now you can edit it with a text editor and correct

for example the name.

After modifying and saving the script file, open a new lbr file and

use SCRIPT to import the script file.

--

Mit freundlichen Gruessen / Best regards

Richard Hammerl

  CadSoft Support -- hotline@cadsoft.de

  FAQ: http://www.cadsoft.de/faq.htm