Open Sch & Brd files together

Tilmann Reh wrote:

The real old-fashioned user doesn't use the Eagle control panel to

navigate to a project.

 

The centralized organization introduces several years ago is not

appropriate in many cases.

 

Ack.

 

For us, this means we must put the files into the EAGLE project*

directory for working on them, and don't forget to move them back into*

our project hierarchy afterwards.

as you know, I never move anything "into the EAGLE project directory"

simply because there is no dedicated Eagle directory in my setup.

Using my favourite file manager, I navigate to the directory where the

brd/sch/epf/lbr... are located and start Eagle from there - usually by

passing the name of the epf to Eagle (Windows: epf linked to Eagle

with %1 in the command or "sendto" folder). The Eagle "project"

directory (Directories.Epf from eaglerc) is simply the current

directory ".", and other directory settings also contain ".".

IMO this method is much more efficient than the Cadsoft suggestion if

you have a large file tree containing also other files than Eagle

projects.

A drawback is the uncertain "current directory" when using the sendto

menu, and "." might be not obvious for some user.

I refresh the claim for better handling of arbitrary located projects

in a new thread in eagle.suggest.eng.

This also applies to many settings in the eaglerc file, e.g. the

Directories.* entries - one might want to have different path settings

for different projects. IMO these directories are no "user" settings

but "project" settings. Well - many users will use the same

directories for all projects, so it's convenient for them.

 

...but if there was a way to have them different between projects, it

would satisfy both kinds of users.

 

This could simply be solved by having the "user" settings as

defaults which can be overridden by "project" settings.

Ack.

But how should we control to which file new or changed settings are

stored?

We should discuss this not in this thread but in a suggest group.

Oliver

Tilmann Reh wrote:

The real old-fashioned user doesn't use the Eagle control panel to

navigate to a project.

 

The centralized organization introduces several years ago is not

appropriate in many cases.

 

Ack.

 

For us, this means we must put the files into the EAGLE project*

directory for working on them, and don't forget to move them back into*

our project hierarchy afterwards.

as you know, I never move anything "into the EAGLE project directory"

simply because there is no dedicated Eagle directory in my setup.

Using my favourite file manager, I navigate to the directory where the

brd/sch/epf/lbr... are located and start Eagle from there - usually by

passing the name of the epf to Eagle (Windows: epf linked to Eagle

with %1 in the command or "sendto" folder). The Eagle "project"

directory (Directories.Epf from eaglerc) is simply the current

directory ".", and other directory settings also contain ".".

IMO this method is much more efficient than the Cadsoft suggestion if

you have a large file tree containing also other files than Eagle

projects.

A drawback is the uncertain "current directory" when using the sendto

menu, and "." might be not obvious for some user.

I refresh the claim for better handling of arbitrary located projects

in a new thread in eagle.suggest.eng.

This also applies to many settings in the eaglerc file, e.g. the

Directories.* entries - one might want to have different path settings

for different projects. IMO these directories are no "user" settings

but "project" settings. Well - many users will use the same

directories for all projects, so it's convenient for them.

 

...but if there was a way to have them different between projects, it

would satisfy both kinds of users.

 

This could simply be solved by having the "user" settings as

defaults which can be overridden by "project" settings.

Ack.

But how should we control to which file new or changed settings are

stored?

We should discuss this not in this thread but in a suggest group.

Oliver