element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Definitive guide to Eagle.scr Eaglerc.usr Eagle,epf
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 8 replies
  • Subscribers 179 subscribers
  • Views 1180 views
  • Users 0 members are here
Related

Definitive guide to Eagle.scr Eaglerc.usr Eagle,epf

Former Member
Former Member over 14 years ago

I suggest that a definitive guide is created that explains the interaction

of the files Eagle.scr Eaglerc.usr Eagle.epf

Less uniformed discussion and support requests will result if this

information is publicised in an easy to understand essay.

 

Spread throughout the HELP and manual is some of the information but it has

not been brought together into one place.

Much of the information needed is implied but not explained.

 

Needed, in one place:

Explanations of precedence,  the order in which these files influence the

editors and each other.

The impact of these interactions e.g changes in Eagle.scr not being

effective because of settings remaining in Eaglerc.usr

Discussion on multiple Eagle.scr and guidance for determining which

Eagle.scr is in use

Locations of the respective files including the effect of environment

variables.

Situations where the hard coded defaults are used.

 

It should include discussion in the context of:

-Project

-Non project

-User (or one of many)

 

The guide should address issues that may arise from networked environments

and multiple users

 

The guide should be initially created as a separate downloadable document.

Released via "announce" and  feedback given via "Beta" forums.

After a few iterations it can be included in the manual.

 

Warren

 

 

 

 

  • Sign in to reply
  • Cancel

Top Replies

  • Former Member
    Former Member over 14 years ago in reply to Former Member +1
    Morten Leikvoll wrote on Wed, 02 February 2011 05:03 Imho, all relevant settings should be under gui control, Nooooo! Have a GUI wrapper if you want, but the underlying settings must always be available…
Parents
  • Former Member
    Former Member over 14 years ago

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

    news:ii9o80$13f$1@cheetah.cadsoft.de...

    >I suggest that a definitive guide is created that explains the interaction

    of the files Eagle.scr Eaglerc.usr Eagle.epf

     

    Hopefully, v6 won't have any of these files. Imho, all

    relevant settings should be under gui control, and hopefully everything is

    stored either:

    -default global options (first time use, could be included in the binaries,

    but would be better to allow company preferred options like network paths)

    -user spesific global options (copied from default at first use, then

    modified to users preference)

    -project specific parameters together with brd and sch (in one file).

     

    I guess as you move down one level, you should be able to override the

    levels above, but not overwrite. And maybe the above levels should be able

    to lock parameters so lower won't be able to change them.

     

    Brief example1, brd grid:

    -default global:1mm,visible,dot style

    -user spesific:(as default)

    -projct specific:0.1inch (size overridden, but using 'visible' and 'dot'

    from levels above)

     

    Brief example2, paths:

    -default

    global:projectpath=
    mynetwork\projects\%activeproject%\proj,libpath="
    mynetwork\common\Eagle\libs";"
    mynetwork\projects\%activeproject%\libs"

    -user spesific:projectpath=c:\temp\Eagle\proj (libpath taken from above

    level)

    -project specific:libpath=%eaglerootdir%\lib (keeping projectpath from user

    spesific level)

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    Morten Leikvoll wrote on Wed, 02 February 2011 05:03

    Imho, all relevant settings should be under gui control,

     

    Nooooo!

     

    Have a GUI wrapper if you want, but the underlying settings must always be

    available in something like the eagle.scr file that can be automatically

    copied, edited, archived, manipulated from scripts, etc.

     

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    Morten Leikvoll wrote on Wed, 02 February 2011 05:03

    Imho, all relevant settings should be under gui control,

     

    Nooooo!

     

    Have a GUI wrapper if you want, but the underlying settings must always be

    available in something like the eagle.scr file that can be automatically

    copied, edited, archived, manipulated from scripts, etc.

     

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Children
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    Am 02.02.2011 17:33, schrieb Olin Lathrop:

    Nooooo!

     

    Have a GUI wrapper if you want, but the underlying settings must always be

    available in something like the eagle.scr file that can be automatically

    copied, edited, archived, manipulated from scripts, etc.

     

    I agree wholeheartedly. We have MANY users here that stay for a few

    months and then are replaced by other users with new PCs, so as

    administrator I have to install or reinstall EAGLE quite often. At the

    moment this is just done by copying all files to the new PC and that's

    it (or even by not copying anything, but just starting the thing from

    the server). VERY efficient, very quick. If files like EAGLE.SCR or the

    like would not be available any more, the whole installation would need

    LOTS of steps with the GUI to get it to work properly. So please keep

    the WONDERFUL text files that are SO useful for administration.

     

    Andreas Weidner

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    Olin Lathrop <eagle@embedinc.com> wrote:

    Morten Leikvoll wrote on Wed, 02 February 2011 05:03

    >> Imho, all relevant settings should be under gui control,

     

    Nooooo!

     

    Have a GUI wrapper if you want, but the underlying settings must always be

    available in something like the eagle.scr file that can be automatically

    copied, edited, archived, manipulated from scripts, etc.

     

    Yea I agree that all config files should be human readable for the skilled

    computerist, but GUi controlled.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 14 years ago in reply to Former Member

     

    "Olin Lathrop" <eagle@embedinc.com> wrote in message

    news:iic10c$kcs$1@cheetah.cadsoft.de...

    Morten Leikvoll wrote on Wed, 02 February 2011 05:03

    >> Imho, all relevant settings should be under gui control,

     

    Nooooo!

     

    Have a GUI wrapper if you want, but the underlying settings must always be

    available in something like the eagle.scr file that can be automatically

    copied, edited, archived, manipulated from scripts, etc.

     

     

    I propose that all settings (1 or more files) to be accessible from one ULP.

    This way a GUI could be designed and easy changed if new settings are to be

    added in the configuration.

     

     

     

    --

    Silviu Epure

    "Dunarea de Jos" University of Galati, Romania

    http://www.etc.ugal.ro/sepure

     

     

     

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    Silviu Epure wrote on Thu, 03 February 2011 11:11

    "Olin Lathrop" <<private_email>> wrote in message

    news:iic10c$kcs$<private_email>...

    Morten Leikvoll wrote on Wed, 02 February 2011 05:03

    >> Imho, all relevant settings should be under gui control,

     

    Nooooo!

     

    Have a GUI wrapper if you want, but the underlying settings must

    always be

    available in something like the eagle.scr file that can be

    automatically

    copied, edited, archived, manipulated from scripts, etc.

     

    I propose that all settings (1 or more files) to be accessible from one

    ULP.

    This way a GUI could be designed and easy changed if new settings are

    to be

    added in the configuration.

     

     

    I agree.

     

    James.

    --

    James Morrison  ~~~  Stratford Digital

     

    Specializing in CadSoft EAGLE

    • Online Sales to North America

    • Electronic Design Services

    • EAGLE Enterprise Toolkit

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube