Open Sch & Brd files together

Am 24.02.2010 21:25, schrieb Olin Lathrop:

Alexander Horst wrote on Wed, 24 February 2010 14:58

A reason might be another user, who just wants to be asked again. So

adding it as an option would solve the problem for any working style.

 

But that's no reason at all without a reason why a user might want to be

asked again. If you always want to open them together, then there is never

any need to ask and nobody would want or need to be asked again. Can't you

see what you're saying is circular reasoning?

Sure it is. But isn't the purpose of options to allow a more heterogenous

user base to be happy with the software?

Usually I want them to be opened together. Tomorrow I may want to do it

differently for whatever reason. So why not make it switchable?

Alexander Horst wrote on Wed, 24 February 2010 15:38

Usually I want them to be opened together. Tomorrow I may want to do

it

differently for whatever reason.

OK, what reason?

Quote:

So why not make it switchable?

Because it's just silly superstition unless you can come up with a valid

reason to ever open one file without the other.

I can think of alot of things that would never make sense for Eagle to do,

and I don't want a switch to disable each one.

--

Browser access to CadSoft Support Forums at http://www.eaglecentral.ca

Oliver Betz schrieb:

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.

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.

Tilmann

Alexander Horst schrieb:

Often, there is no epf, e.g. when opening a sch&brd pair, which was sent

by email. In this case I very often run into the behavior as described by

Silviu.

This could be solved if EAGLE would load some kind of default "project"

settings when a sch/brd file is opened directly (instead of a project).

Tilmann

Silviu Epure schrieb:

"Richard Hammerl" <ric@cadsoft.de> wrote in message

news:hm3akc$b1l$1@cheetah.cadsoft.de...

Well this is no problem at all, if you don't use the Windows Explorer

for opening EAGLE files. Why don't you start EAGLE and load the files

with File/Open? Or am I to old-fashioned here?

 

 

Because Cadsoft's choise is to NOT USE Control Panel as FILE EXPLORER, but

as "project explorer".

I say-it for n'th times: Eagle Control Panel is an "feature" with low-to

none use, as it is now.

If there was a directory tree, or if Control Panel would display and permit

opening other files too, maybe. But for now it's not usable this way.

 

I want to open a file, not to open Eagle to open a file. It's a matter of

eficiency....

 

 

Your "eficiency" is rubbish. If in windows explorer you click on an

excel file for example, the explorer calls excel.exe which in turn opens

the excel file. Same goes with eagle. So you should be a little more

precise.

And, by the way, your tenor goes on my nerves.

--

Gruß / regards

Joern

Olin Lathrop schrieb:

Alexander Horst wrote on Wed, 24 February 2010 15:38

Usually I want them to be opened together. Tomorrow I may want to do

it

differently for whatever reason.

 

OK, what reason?

 

Quote:

So why not make it switchable?

 

Because it's just silly superstition unless you can come up with a valid

reason to ever open one file without the other.

 

I can think of alot of things that would never make sense for Eagle to do,

and I don't want a switch to disable each one.

Assuming that both files exist and open I don't need a swich for the

reason that it is the same amount of "work" to click on the switch or

just to close one file.

And for this sos (single open switch)   you need a selector whether

to open the board or the sheet and a switch to select whether the

control panel should be opened...

--

Gruß / regards

Joern

Il 24/02/2010 18.09, Olin Lathrop ha scritto:

KP wrote on Wed, 24 February 2010 11:54

Obviously you would also need a way to somehow revert your selection.

 

You do? Can you explain a reason why you'd ever not want both the

schematic and board open together, once they both exist?

I can imagine only 2 situations when I might want to open only one of

the respective sch or brd files.

1) When I run into some inconsistencies between sch and brd. Then I

would modify the odd file to match the counterpart file. Change the

design (add, delete, rename...) and run Erc until you have fixed the

errors, save both files and you are ok for the future. Suppose all this

can be done having both sch and brd files open, so this might not be a

valid case.

2) When doing some very special modifications. Comes into my mind PCB RF

Antennas. Maybe I want to replace the Antenna on my design. I might copy

it from another brd file and paste to my new design, maybe replacing

what I already have. Rename traces and symbols approprietly and run Erc

to keep sch happy. To do all this I might want to work on brd file alone.

I'd prefer much more that Eagle opened both sch & brd together as

default (if both exist). I'd then just close the one I don't need to

make these low level "hacks" (which I don't promote here).

How Eagle behaves now I can have open sch from one design and brd from

another design (ex. front.sch and back.brd together). Modifying either

of these 2 files would create future Erc errors...

Kim

Joern Paschedag wrote:

Silviu Epure schrieb:

"Richard Hammerl" <ric@cadsoft.de> wrote in message

news:hm3akc$b1l$1@cheetah.cadsoft.de...

Well this is no problem at all, if you don't use the Windows Explorer

for opening EAGLE files. Why don't you start EAGLE and load the files

with File/Open? Or am I to old-fashioned here?

 

 

Because Cadsoft's choise is to NOT USE Control Panel as FILE EXPLORER, but

as "project explorer".

I say-it for n'th times: Eagle Control Panel is an "feature" with low-to

none use, as it is now.

If there was a directory tree, or if Control Panel would display and permit

opening other files too, maybe. But for now it's not usable this way.

But wouldn't it be inefficient for Cadsoft to implement the zillionth

file manager and for the user to learn it?

I want to open a file, not to open Eagle to open a file. It's a matter of

eficiency....

 

Your "eficiency" is rubbish. If in windows explorer you click on an

excel file for example, the explorer calls excel.exe which in turn opens

the excel file. Same goes with eagle. So you should be a little more

No, that's not so simple with Eagle since an Eagle project consists of

many files compared to one Excel file.

And you can hold many Excel files in one directory, but only ne Eagle

project due to the magic name "eagle.epf".

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

"Joern Paschedag" <jpaschedag@t-online.de> wrote in message

news:hm5ean$uk9$1@cheetah.cadsoft.de...

 

Your "eficiency" is rubbish. If in windows explorer you click on an excel

file for example, the explorer calls excel.exe which in turn opens the

excel file. Same goes with eagle. So you should be a little more precise.

And, by the way, your tenor goes on my nerves.

Hey, I've just give you a good example where a common stupid user like me

(who uses computer 10h/day, 30days/month, for about 10 years now, most of

the time for electronics) find behaviour of the Eagle "strange".

I think this way: "I want to open the schematic with ultrasonic emitter"...

and I do the simplest way to open that schematic...

I don't think that "I should find the .epf file for the project that I've

once created to make a ultrasonic emitter"

And to be usefull. Eagle Control Panel should at least support pdf and

images....Could be displayed/preview on the "white (now - 90%of time) area

of the Control Panel"