v6 ignored Options Directories entries

Brett Holden wrote:

I think that when somebody installs v6 alongside v5 that v6 should run

exclusively and not use v5 libraries.

 

I say this because when I installed v6 it wanted to use my old v5

libraries.

 

I copied my projects and libraries to entirely new directories so

that my old ones would not get fouled up and I made the appropriate

changes to the control panel "Options Directories", but Eagle IGNORED

my changes that pointed to the v6 libraries. Instead of using my v6

libraries, Eagle v6 continued to use my old v5 libraries from a

non-specified directory.

 

Fortunately I realized that my old libraries were in use and

proceeded to fix the problem.

 

"Use -*" (enter) and then "Use *" took care of the problem, but WHY

should that rigamarole be necessary??.

 

This is not a suggestion so much as it is a bug report. It's an

accident waiting to happen. I remember the exact thing happening as I

upgraded from v4 to v5.

This has been highligted a few times since the v6 betas were initially

released and I agree that Cadsoft need to mitigate the potential for these

inter-version traps.

It's just bad customer relations and there are many early adopters of v6

sufferring.

Although it is a trap, it could be argued Eagle works reasonaibly and it is

a user issue. That said, I feel that a document could have been made

available that guided their customers around these 'gotcha's'.

In your case Brett, when you replicated your projects, the eagle.epf files

were replicated and they contain the paths to that projects libraries used

to that point which are the v5 paths.

So you opened the project in v6 and the epf file made available the v5

libraries listed within it. The .  Thats why  "Use -*" (enter) and then "Use

*" worked..It closed the v5 libs and opened those you specified in (v6)

Options/Directories. Subsequently the eagle.epf reflected those paths to the

v6 libraries.

There is a second trap related to this one. If, in v5, you closed Eagle with

a project open, then the eaglerc.usr file will remember this project.

When you open v6 and provided you did not establish a different place for

the v6 eaglerc.usr file to reside  then v6 will read the eaglerc.usr file

(written with v5) and open your v5 project as it contains te full path. If

you dont realise this and subsequently 'save', you  have  now converted the

v5 file to v6.

I feel if CadSoft diverted some of its current support effort to getting

these upgrade issues publicised the number of support calls would reduce and

make more time available for other pressing issues.

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

Brett Holden wrote:

I think that when somebody installs v6 alongside v5 that v6 should run

exclusively and not use v5 libraries.

 

I say this because when I installed v6 it wanted to use my old v5

libraries.

 

I copied my projects and libraries to entirely new directories so

that my old ones would not get fouled up and I made the appropriate

changes to the control panel "Options Directories", but Eagle IGNORED

my changes that pointed to the v6 libraries. Instead of using my v6

libraries, Eagle v6 continued to use my old v5 libraries from a

non-specified directory.

 

Fortunately I realized that my old libraries were in use and

proceeded to fix the problem.

 

"Use -*" (enter) and then "Use *" took care of the problem, but WHY

should that rigamarole be necessary??.

 

This is not a suggestion so much as it is a bug report. It's an

accident waiting to happen. I remember the exact thing happening as I

upgraded from v4 to v5.

This has been highligted a few times since the v6 betas were initially

released and I agree that Cadsoft need to mitigate the potential for these

inter-version traps.

It's just bad customer relations and there are many early adopters of v6

sufferring.

Although it is a trap, it could be argued Eagle works reasonaibly and it is

a user issue. That said, I feel that a document could have been made

available that guided their customers around these 'gotcha's'.

In your case Brett, when you replicated your projects, the eagle.epf files

were replicated and they contain the paths to that projects libraries used

to that point which are the v5 paths.

So you opened the project in v6 and the epf file made available the v5

libraries listed within it. The .  Thats why  "Use -*" (enter) and then "Use

*" worked..It closed the v5 libs and opened those you specified in (v6)

Options/Directories. Subsequently the eagle.epf reflected those paths to the

v6 libraries.

There is a second trap related to this one. If, in v5, you closed Eagle with

a project open, then the eaglerc.usr file will remember this project.

When you open v6 and provided you did not establish a different place for

the v6 eaglerc.usr file to reside  then v6 will read the eaglerc.usr file

(written with v5) and open your v5 project as it contains te full path. If

you dont realise this and subsequently 'save', you  have  now converted the

v5 file to v6.

I feel if CadSoft diverted some of its current support effort to getting

these upgrade issues publicised the number of support calls would reduce and

make more time available for other pressing issues.

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

Am 31.12.2011 02:30, schrieb Warren Brayshaw:

Brett Holden wrote:

>> I think that when somebody installs v6 alongside v5 that v6 should run

>> exclusively and not use v5 libraries.

>>

>> I say this because when I installed v6 it wanted to use my old v5

>> libraries.

>>

>> I copied my projects and libraries to entirely new directories so

>> that my old ones would not get fouled up and I made the appropriate

>> changes to the control panel "Options Directories", but Eagle IGNORED

>> my changes that pointed to the v6 libraries. Instead of using my v6

>> libraries, Eagle v6 continued to use my old v5 libraries from a

>> non-specified directory.

>>

>> Fortunately I realized that my old libraries were in use and

>> proceeded to fix the problem.

>>

>> "Use -*" (enter) and then "Use *" took care of the problem, but WHY

>> should that rigamarole be necessary??.

>>

>> This is not a suggestion so much as it is a bug report. It's an

>> accident waiting to happen. I remember the exact thing happening as I

>> upgraded from v4 to v5.

 

This has been highligted a few times since the v6 betas were initially

released and I agree that Cadsoft need to mitigate the potential for these

inter-version traps.

It's just bad customer relations and there are many early adopters of v6

sufferring.

 

Although it is a trap, it could be argued Eagle works reasonaibly and it is

a user issue. That said, I feel that a document could have been made

available that guided their customers around these 'gotcha's'.

 

In your case Brett, when you replicated your projects, the eagle.epf files

were replicated and they contain the paths to that projects libraries used

to that point which are the v5 paths.

So you opened the project in v6 and the epf file made available the v5

libraries listed within it. The .  Thats why  "Use -*" (enter) and then "Use

*" worked..It closed the v5 libs and opened those you specified in (v6)

Options/Directories. Subsequently the eagle.epf reflected those paths to the

v6 libraries.

 

There is a second trap related to this one. If, in v5, you closed Eagle with

a project open, then the eaglerc.usr file will remember this project.

When you open v6 and provided you did not establish a different place for

the v6 eaglerc.usr file to reside  then v6 will read the eaglerc.usr file

(written with v5) and open your v5 project as it contains te full path. If

you dont realise this and subsequently 'save', you  have  now converted the

v5 file to v6.

 

I feel if CadSoft diverted some of its current support effort to getting

these upgrade issues publicised the number of support calls would reduce and

make more time available for other pressing issues.

 

Warren

 

>

Unfortunately this problem exists since a very long time. There have

been a lot of discussions about the eaglerc.usr und .epf files but

nothing has changed. In win OS the eagle -U parameter helps a little but

once you forget the eaglerc.usr originally created in your user

directory you run into the same problem again.

I must run different versions of eagle installations in parallel and the

versions are in different directories or even different disks but one

must watch hell if opening a file just with a double click.

Eagle V6 has a new structure but imo this issue needs a new structure as

well.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag