5.8 Not Remembering Which Libraries Are In Use

On 4/21/2010 3:19 AM, Nic Jones wrote:

Since upgrading to 5.8, Eagle doesn't seem to remember which of my

libraries I've selected as "Use"

 

I'm running Eagle on Mac OS X 10.6.3, and have some libraries local

("Applications/EAGLE/lbr/") and some libraries on a network share when

I'm at work. ("/Volumes/Network Drive/EAGLELibs/")

 

I can go through and "Use" libraries, quit Eagle, re-launch it and the

change doesn't stick. Nothing in a folder greater than one level deep

(i.e. "lbr/5.8/19inch.lbr" will stay "Use"d and libraries. Nothing one

level deep (i.e. "lbr/Nic.lbr") will stay de-"Use"d.

 

Where does Eagle store the list of libraries that are in use? Maybe I

could set things up and lock the file to stop Eagle buggering it up.

It's a royal pain to go through every folder and "Use all" again. (Why

can't I make multiple selections in the list? Why does Eagle let me Use

libraries that are in old formats and it can't use? Why isn't "Use all"

recursive? Why is the sort order some bizarre

folders-first-capitals-before-lower-case thing instead of alphabetical?)

 

In a related matter, when I boot Eagle without having the network share

mounted, it complains about missing include directories, and offers to

create them. The default action is to create them, which would make

directories in the /Volumes/ directory. This is bad behaviour - creating

directories in /Volumes means that when the network share is mounted,

the system either has to overwrite (potentially destroying user data)

or, as is the case, mount with a different path. Eagle will then be

stuck silently pointing at the folder it created instead of the network

share.

 

Cheers,

Nic Jones,

Ocean Controls

Hi Nic,

When you open EAGLE without a project and you create a new project by

default all libraries will be available. However, if EAGLE opens with a

project then it will first read the EAGLE.epf file checking which

libraries were in use for that particular project, if while working on a

project you drop some of the libraries then, when you open that project

EAGLE will remember the libraries you were using.

To put it another way, EAGLE doesn't save information on what libraries

are being used globally. EAGLE saves that information on a Project by

Project  basis.

To answer your other concern, you don't have to create that new

directory EAGLE offers to make, simply click the red X in Windows to

close the screen that has popped the error message.

It's also possible to point EAGLE to the directories you want to use for

libraries that way you don't have to worry about which file is where and

mixing them in the wrong folder.

The steps for setting up the directory are listed below:

In the EAGLE control panel click Options -> Directories

You will see several fields each pointing to the various locations of

the files needed. So if you want to able to access libraries from both

the server and your personal file type the following into the Libraries

fiels.

PATH_SOURCE_1;PATH_SOURCE_2;PATH_SOURCE_3; etc.

You can have links to several source folders simply use the semi-colon

to delimit.

Hope this helps,

Regards,

Jorge Garcia

On 4/21/2010 3:19 AM, Nic Jones wrote:

Since upgrading to 5.8, Eagle doesn't seem to remember which of my

libraries I've selected as "Use"

 

I'm running Eagle on Mac OS X 10.6.3, and have some libraries local

("Applications/EAGLE/lbr/") and some libraries on a network share when

I'm at work. ("/Volumes/Network Drive/EAGLELibs/")

 

I can go through and "Use" libraries, quit Eagle, re-launch it and the

change doesn't stick. Nothing in a folder greater than one level deep

(i.e. "lbr/5.8/19inch.lbr" will stay "Use"d and libraries. Nothing one

level deep (i.e. "lbr/Nic.lbr") will stay de-"Use"d.

 

Where does Eagle store the list of libraries that are in use? Maybe I

could set things up and lock the file to stop Eagle buggering it up.

It's a royal pain to go through every folder and "Use all" again. (Why

can't I make multiple selections in the list? Why does Eagle let me Use

libraries that are in old formats and it can't use? Why isn't "Use all"

recursive? Why is the sort order some bizarre

folders-first-capitals-before-lower-case thing instead of alphabetical?)

 

In a related matter, when I boot Eagle without having the network share

mounted, it complains about missing include directories, and offers to

create them. The default action is to create them, which would make

directories in the /Volumes/ directory. This is bad behaviour - creating

directories in /Volumes means that when the network share is mounted,

the system either has to overwrite (potentially destroying user data)

or, as is the case, mount with a different path. Eagle will then be

stuck silently pointing at the folder it created instead of the network

share.

 

Cheers,

Nic Jones,

Ocean Controls

Hi Nic,

When you open EAGLE without a project and you create a new project by

default all libraries will be available. However, if EAGLE opens with a

project then it will first read the EAGLE.epf file checking which

libraries were in use for that particular project, if while working on a

project you drop some of the libraries then, when you open that project

EAGLE will remember the libraries you were using.

To put it another way, EAGLE doesn't save information on what libraries

are being used globally. EAGLE saves that information on a Project by

Project  basis.

To answer your other concern, you don't have to create that new

directory EAGLE offers to make, simply click the red X in Windows to

close the screen that has popped the error message.

It's also possible to point EAGLE to the directories you want to use for

libraries that way you don't have to worry about which file is where and

mixing them in the wrong folder.

The steps for setting up the directory are listed below:

In the EAGLE control panel click Options -> Directories

You will see several fields each pointing to the various locations of

the files needed. So if you want to able to access libraries from both

the server and your personal file type the following into the Libraries

fiels.

PATH_SOURCE_1;PATH_SOURCE_2;PATH_SOURCE_3; etc.

You can have links to several source folders simply use the semi-colon

to delimit.

Hope this helps,

Regards,

Jorge Garcia