v6 ignored Options Directories entries

Am 30.12.2011 23:54, schrieb Brett Holden:

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

exclusively and not use v5 libraries.

 

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 problem happens with LOTS of people and EVERY major program update

since YEARS (and also with every OTHER program on earth). In most cases,

the user KNOWS that one may not overwrite old projects that still need

to be edited with the older version, but sometimes the phone rings,

something else happens and voila! you forget and have ruined your old

files by just accidentally pressing CTRL+S. Too bad! (And yes, I myself

was also swearing wildly once when doing an update from 4 to 5. Luckily,

I had some backups and only had to throw three hours of work in the bin)

This is again a case of bad GUI in case of problems: Here, the user

SHOULD be notified, but isn't, probably resulting in problems. There are

several simple possibilities to get this done properly (and lots of

programs use at least the following point 1):

  1. EAGLE just KNOWS the version with which a newly opened file was

     previously created. And it knows its OWN version. And CadSoft

     KNOWS between which versions (even minor version changes) the

     data structure was changed or expanded. Therefore,

      - if there is a FILE data structure change between the saved

        file and the current EAGLE version, the user is notified

        with a dialog box like: 'This file was created with an older

        version of EAGLE. If you change and save it, you might not be

        able to reopen it with the old EAGLE version. Proceed with

        the file loading? '.

     THAT is quite easy to do, BUT has the problem that the user

     might easily FORGET this message during viewing. Accidentally

     pressing CTRL+S does STILL ruin editability with older versions.

  2. To circumvent this, a similar question could be asked AGAIN

     when the user wants to SAVE the file ('Do you really want to

     overwrite the existing file? Reopening it with older EAGLE

     versions might not be possible afterwards. '). Yes,

     this MIGHT be a nuisance, but this save warning is displayed

     only ONCE per file IF there might be a version problem. After

     the file has REALLY been saved with the new version, these

     questions will cease completely until a new (not downward-

     compatible) version is used. That should be OK (at least in

     MY opinion).

  3. Some other programs use different schemes, which I myself do NOT

     like much:

      - In case file versions differ, the user is informed during

        file loading (as stated above). To prevent accidental

        overwrites, the file is opened write-protected. Before

        saving it again, write-protection must be disabled manually

        in some file option dialog. [Disadvantage: There must be

        this write-protection option somewhere]

      - In case file versions differ, the user is informed during

        file loading (as stated above). To prevent accidental

        overwrites, the file is opened like a NEW file (without

        proper file name), so just saving does NOT work, because the

        user is ALWAYS asked for a new file name. [Disadvantage:

        The user MUST enter a file name. This needs quite some

        typing, and one MIGHT even have forgotten the name in the

        meantime]

Therefore, the combination of (1) and (2) should make version problems a

thing of the past. And for the guys who really HATE to be asked such

questions, why not implement my suggestion from the post 'EAGLE GUI (7):

Unnerving failure behaviour' and put a 'Don't show this message again'

checkbox in the question dialog (2)?

The above is VERY easy to implement and protects the user from ACCIDENTS

(this is what a good GUI should do). Of course the new EAGLE version

would STILL use the old libraries and not its own ones. But this CAN be

circumvented with the '-U' switch. If the user wants to run different

EAGLE versions in paralled, put some information about that in the

manual. This way, newbies cannot ACCIDENTALLY overwrite their projects,

and experts can take parallel-install information from the manual. I

cannot tell whether there would still be awkward problems when using

PROJECTS - I just HATE the behaviour with projects due its multiple

drawbacks, and therefore our institute doesn't use them...

Andreas Weidner

Am 04.01.2012 06:52, schrieb Grzegorz Zalot:

Hello Joern Paschedag !:

 

>> The -U parameter was imo created during Ver.5 testing. I didn't know how

>> to use this parameter by that time but got an answer from cadsoft that

>> it "sets" a new path for the "eaglerc.usr" file. To test that I gave it

>> a new name too and that worked.

>> So since that time I use somethimg like "-U F:\Eagle-6.0.2\

>> eaglerc602.usr" to place the file in the eagle Ver.6 dirctory.

>> Same goes for my version 5.

 

Brrrrrr, workaround again ....

 

Yes, but I have to run 3 Versions of eagle, 4, 5 and 6 and so this is at

least a little way out...

>> Warren Brayshaw has explained that more detailed.

>> So if users place the -U parameter with "my" extention into the

>> properties of the launcher they should change the name of the

>> eaglerc.usr file first before starting eagle, otherwise they run against

>> the wall again.

 

Exactly here is the problem.

 

BR

Well one must know what one is doing (hopefully)

I have to watch out carefully since some clients send version 4.x files

and insist of return in this version.

Right now I'm working still with v5, because of the many reported

troubles in v6, which was imo released too early.

If there is time I test with v6 or try to follow reports but so far I

had none of the so many reported crashes on my windows xp.

Unfortunately many people reporting errors witout mention the machine

and software they use. That makes it even more difficult for cadsoft to

locate errors.

Sorry but I am drifting OT.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Hello Joern Paschedag !:

The -U parameter was imo created during Ver.5 testing. I didn't know how

to use this parameter by that time but got an answer from cadsoft that

it "sets" a new path for the "eaglerc.usr" file. To test that I gave it

a new name too and that worked.

So since that time I use somethimg like "-U F:\Eagle-6.0.2\

eaglerc602.usr" to place the file in the eagle Ver.6 dirctory.

Same goes for my version 5.

Brrrrrr, workaround again ....

Warren Brayshaw has explained that more detailed.

So if users place the -U parameter with "my" extention into the

properties of the launcher they should change the name of the

eaglerc.usr file first before starting eagle, otherwise they run against

the wall again.

Exactly here is the problem.

BR

--

Grzegorz Zalot

complex ltd.

office tel/fax : +48 32 2505840

mobil : +48 501 301515

http://www.complex.org.pl/

Am 03.01.2012 07:56, schrieb Grzegorz Zalot:

Hello Brett Holden !:

>> 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.

 

.....

 

The problem is really primitive and ... IMHO stupid. In fact all EAGLE

instances use THE SAME eaglerc.usr file !!!!! Of course in v5 the libs

are in v5 subfolders, in v6 - sure not the same. Of course the danger to

make unwanted update of the libs is really high.

 

I am afraid this stupis behaviour is not aa incident ... I guess CadCoft

want to push more peopple to buy new v6. Why ? Because changing the name

of the usr file is really primitive.

 

My suggestion : if CadSoft still want to use same name of the usr file

we have to use some workaround, f.i. batch file or ... use an hex editor

and change the name of the usr file !!!! This is 1-2 minutes time and

works perfectly.

 

IMHo this is really a stupid problem ... and sure totally unnecessary.

 

best regards

Happy New Year everyone

The -U parameter  was imo created during Ver.5 testing. I didn't know

how to use this parameter by that time but got an answer from cadsoft

that it "sets" a new path for the "eaglerc.usr" file. To test that I

gave it a new name too and that worked.

So since that time I use somethimg like "-U F:\Eagle-6.0.2\

eaglerc602.usr" to place the file in the eagle Ver.6 dirctory.

Same goes for my version 5.

Warren Brayshaw has explained that more detailed.

So if users place the -U parameter with "my" extention into the

properties of the launcher they should change the name of the

eaglerc.usr file first before starting eagle, otherwise they run against

the wall again.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Hello Brett Holden !:

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.

.....

The problem is really primitive and ... IMHO stupid. In fact all EAGLE

instances use THE SAME eaglerc.usr file !!!!! Of course in v5 the libs

are in v5 subfolders, in v6 - sure not the same. Of course the danger to

make unwanted update of the libs is really high.

I am afraid this stupis behaviour is not aa incident ... I guess CadCoft

want to push more peopple to buy new v6. Why ? Because changing the name

of the usr file is really primitive.

My suggestion : if CadSoft still want to use same name of the usr file

we have to use some workaround, f.i. batch file or ... use an hex editor

and change the name of the usr file !!!! This is 1-2 minutes time and

works perfectly.

IMHo this is really a stupid problem ... and sure totally unnecessary.

best regards

--

Grzegorz Zalot

complex ltd.

office tel/fax : +48 32 2505840

mobil : +48 501 301515

http://www.complex.org.pl/

"Warren Brayshaw" <warrenbrayshaw@paradise.net.nz> wrote in message

news:jdt3r8$d95$1@cheetah.cadsoft.de...

Brett Holden wrote:

 

>> ..............Here is text from the manual, page 113:

>> "It is possible to start EAGLE with the command line option -U which

>> can be used to define the location of the eaglerc file."

>>

>> That does not explain anything to me. I can't use -U if I don't know

>> how. If this goes on much longer I will feel obliged to re-ask this

>> question in the support forum, but maybe somebody can answer me here

>> to get this over with:

>>

>> What is the proper syntax and application for starting Eagle with the

>> -U parameter? (I'm using Windows XP.)

 

Hi Brett

Mario's reference is good.

 

Some further clarification.

1) When you use the  -U option you can name the 'user file' anything as it

does then not have to remain as eaglerc.usr. In the example Richard

provided

it is named 'myeaglerc.usr'.

2) If there are spaces in your path to the file then double quotes are

needed. I launch from a desktop icon so modified its target (in

properties)

so that it contains the -U option and location of the eaglerc.usr file.

As I have spaces here is my path.

"C:\Documents and Settings\Warren\NewEagle2\bin\eagle.exe" -U"C:\Documents

and Settings\Warren\NewEagle2\eaglerc.usr"

3) Note there is no space after the U

4)If you have multiple Eagle version installs, double clicking a design

file

outside of Eagle cannot be used to launch Eagle as only one version of

Eagle

can be associated with the file type.  You can set up Windows so that if

you

right click on the file (viewed in, say, explorer) then the context menu

lists the multiple Eagle versions you have set up. In this way  you can

launch the appropriate Eagle version from the file but I have not found a

way to make none of them the default. You want no defaults as a double

click, in error, on the file may launch the wrong Eagle version. It is

best

to disable file associations from brd, sch,  lib, usr files.

 

Hope this helps

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

 

That's it, Warren.

I thought Mario's references would be the fix but I was still getting kicked

in the teeth with various error messages, either trying to use the RUN box,

or trying to launch from a desktop icon with modified icon target

properties.

So, thank you for that explicit example, that is exactly what I needed. I

was having trouble because there is a space in my directory path and I had

forgotten the need for double quotes.

The -U option is working now (and no thanks to Cadsoft's documentation).

Cadsoft apparently expects somebody using their product to be a computer

guru, or else suffer.

Thank you to all who responded.

Brett Holden wrote:

..............Here is text from the manual, page 113:

"It is possible to start EAGLE with the command line option -U which

can be used to define the location of the eaglerc file."

 

That does not explain anything to me. I can't use -U if I don't know

how. If this goes on much longer I will feel obliged to re-ask this

question in the support forum, but maybe somebody can answer me here

to get this over with:

 

What is the proper syntax and application for starting Eagle with the

-U parameter? (I'm using Windows XP.)

Hi Brett

Mario's reference is good.

Some further clarification.

1) When you use the  -U option you can name the 'user file' anything as it

does then not have to remain as eaglerc.usr. In the example Richard provided

it is named 'myeaglerc.usr'.

2) If there are spaces in your path to the file then double quotes are

needed. I launch from a desktop icon so modified its target (in properties)

so that it contains the -U option and location of the eaglerc.usr file.

As I have spaces here is my path.

"C:\Documents and Settings\Warren\NewEagle2\bin\eagle.exe" -U"C:\Documents

and Settings\Warren\NewEagle2\eaglerc.usr"

3) Note there is no space after the U

4)If you have multiple Eagle version installs, double clicking a design file

outside of Eagle cannot be used to launch Eagle as only one version of Eagle

can be associated with the file type.  You can set up Windows so that if you

right click on the file (viewed in, say, explorer) then the context menu

lists the multiple Eagle versions you have set up. In this way  you can

launch the appropriate Eagle version from the file but I have not found a

way to make none of them the default. You want no defaults as a double

click, in error, on the file may launch the wrong Eagle version. It is best

to disable file associations from brd, sch,  lib, usr files.

Hope this helps

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

"MarioS" <noreply-77933@element14.com> wrote in message

news:610995789.1241325512868348.JavaMail.jive@flmspu-csapp-02.premierfarnell.com...

Please, see this:

 

http://www.eaglecentral.ca/forums/index.php?t=rview&goto=135889&th=42936

 

Saludos y Felices Fiestas!

Aiieee!

Mucho gracias , señor.

About 'command line option -U', please, see this:

http://www.eaglecentral.ca/forums/index.php?t=rview&goto=135889&th=42936

Saludos y Felices Fiestas!

"Warren Brayshaw" <warrenbrayshaw@paradise.net.nz> wrote in message

news:jdo4aj$c3$1@cheetah.cadsoft.de...

Brett Holden wrote:

>> Yup I originally had problem with only the wrong libraries being

>> used. Now I can't seem to get Eagle to use the v6 project folders I

>> established. It wants to open the old schematic files and I don't see

>> an obvious fix...........

>>

>

 

Continuing on from what has be written previously you may still have

problems caused by eaglerc.usr

eaglerc.usr  file also contains the directory paths and when you launch

Eagle it sets those paths into Control Panel/Options/Directories.

 

Have you set up your v5 and v6 versions to launch with the -U option to

specify exactly where the eaglerc.usr for each version resides?

If not each installed version of Eagle will forever be entangled as you

swap

between them due to a single eaglerc.usr being used.

 

Once you have established a separate eaglerc.usr for each version  you can

then proceed to clean up the eaglerc.usr of each of the versions if need

be.

 

I would progress this way.

1) Launch an Eagle version

2)Ensure no Project is selected

3)Check and modify Control Panel/Options/Directories.

3) Save all

4) Control Panel / Refresh.

 

eaglerc.usr should now be correct for that version you are viewing.

 

Then, for v6 and as said previously, as you load a project from a previous

version for the 1st time you have to  "Use -*" (enter) and then

"Use*" to get rid of the library paths to the libraries of the previous

versions (contained in the eagle.epf file you also copied across) and only

present the libraries as defined in the paths in Control

Panel/Options/Directories.

 

Others reading this and who have not followed the thread fully should be

aware that you should not just commence opening v5 projects with v6. After

the obligatory 'backup', replicate your v5 project (a folder with all its

files)  into the v6 project folder and work from that copy as the

eagle.epf

file of that project needs to be personalised for v6.

 

All the best

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

 

Thanks Warren, Joern.

I deleted the Eaglerc.usr file and reloaded and my problems with using ver5

files disappeared. But I would like to know how the -U parameter is

implemented.

I found in the manual (and update notes) where there is such a thing but I

can find no instruction how to use it.

Here is text from the manual, page 113:

"It is possible to start EAGLE with the command line option -U which can be

used to define the location of the eaglerc file."

That does not explain anything to me. I can't use -U if I don't know how.

If this goes on much longer I will feel obliged to re-ask this question in

the support forum, but maybe somebody can answer me here to get this over

with:

What is the proper syntax and application for starting Eagle with the -U

parameter? (I'm using Windows XP.)