EAGLE v8.0 causes icons to revert to classic style w hen subsequently opening v7.7

rachaelp wrote on Tue, 24 January 2017 15:43

Hello,

 

I've been playing about with v8.0 over the last week but today went

back to v7.7 and was presented with a UI that had strange icons I didn't

recognise!

 

Upon checking the settings I found the "Classic icon style" checkbox

was ticked. I presume this is because v8.0 no longer has this so removed

the setting from the EAGLE config file causing it to default on in v7.

Now for some this might be seen as a pro for v8 as they don't like the

new style icons but I do and I don't want to have to keep changing the

setting back and restarting every time I switch from v8.0 to v7.7. Could

you please fix this for the next release?

 

It begs the question, are there any other settings which are

accidentally being altered which might be more subtle and not so easily

spotted?

 

Can you please make sure that v8 preserves the integrity and backwards

compatibility of the config files?

 

Many thanks,

 

Rachael

It sounds like Autodesk didn't fix the problem that has plagued all major

EAGLE upgrades--overwriting the .eaglerc file.  Is it really that hard to

create .eagle8rc and use .eagle8rc for V8 so that new installations don't

trounce over the file?

When you install a brand new version (v7 -> v8) EAGLE should be smart

enough to create the new version of the file and import all the settings

from the older version that can be carried forward (perhaps after asking

the user if they'd like to do this).

With all the other files each user should keep those separate (libraries,

custom ULP's, etc) so that upgrading won't effect them.  But we have no

control over the .eaglerc file and that screws things up every time.  Yes,

there is a command line option to use a new version but that is going to be

missed by 99% of the people.  If EAGLE would just use a config file with

the major version in the filename and the problem is solved.

Cheers,

James.

--

James Morrison  ~~~  Stratford Digital

http://www.stratforddigital.ca

--

EAGLE support forums at http://www.eaglecentral.ca :: Where the EAGLE community meets.

rachaelp wrote on Tue, 24 January 2017 15:43

Hello,

 

I've been playing about with v8.0 over the last week but today went

back to v7.7 and was presented with a UI that had strange icons I didn't

recognise!

 

Upon checking the settings I found the "Classic icon style" checkbox

was ticked. I presume this is because v8.0 no longer has this so removed

the setting from the EAGLE config file causing it to default on in v7.

Now for some this might be seen as a pro for v8 as they don't like the

new style icons but I do and I don't want to have to keep changing the

setting back and restarting every time I switch from v8.0 to v7.7. Could

you please fix this for the next release?

 

It begs the question, are there any other settings which are

accidentally being altered which might be more subtle and not so easily

spotted?

 

Can you please make sure that v8 preserves the integrity and backwards

compatibility of the config files?

 

Many thanks,

 

Rachael

It sounds like Autodesk didn't fix the problem that has plagued all major

EAGLE upgrades--overwriting the .eaglerc file.  Is it really that hard to

create .eagle8rc and use .eagle8rc for V8 so that new installations don't

trounce over the file?

When you install a brand new version (v7 -> v8) EAGLE should be smart

enough to create the new version of the file and import all the settings

from the older version that can be carried forward (perhaps after asking

the user if they'd like to do this).

With all the other files each user should keep those separate (libraries,

custom ULP's, etc) so that upgrading won't effect them.  But we have no

control over the .eaglerc file and that screws things up every time.  Yes,

there is a command line option to use a new version but that is going to be

missed by 99% of the people.  If EAGLE would just use a config file with

the major version in the filename and the problem is solved.

Cheers,

James.

--

James Morrison  ~~~  Stratford Digital

http://www.stratforddigital.ca

--

EAGLE support forums at http://www.eaglecentral.ca :: Where the EAGLE community meets.

With all the other files each user should keep those separate (libraries,

custom ULP's, etc) so that upgrading won't effect them.  But we have no

control over the .eaglerc file and that screws things up every time.  Yes,

there is a command line option to use a new version but that is going to be

missed by 99% of the people.  If EAGLE would just use a config file with

the major version in the filename and the problem is solved.

 

Cheers,

 

James.

 

Hi James,

You beat me to it. I'll put in a request with a variant of your

recommended solution so that this can be implemented soon.

It's been too long for such a small issue that could be easily rectified.

Best Regards,

Jorge Garcia