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 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
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • 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) Open Sch & Brd files together
  • 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 72 replies
  • Subscribers 180 subscribers
  • Views 7203 views
  • Users 0 members are here
Related

Open Sch & Brd files together

k.portman
k.portman over 15 years ago

Is there a way to open an existing Sch & Brd file together, by default.

When I double click either Sch or Brd file name on the Eagle Control

Panel it asks "Do you also want to load xxx.brd?" (or xxx.sch). I always

respond Yes, sofar never had a need to respond No.

 

Is there a eaglerc.usr setting to force (or make as default behaviour)

the opening of Brd & Sch files together. If not, could it be

implemented. Much requested for!!!

 

Kim

 

  • Sign in to reply
  • Cancel
Parents
  • dukepro
    dukepro over 15 years ago

    On 02/25/2010 02:16 AM, Tilmann Reh wrote:

    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

     

    Alexander & Tilmann,

     

    All very good points.

     

    A checkbox in the dialog "Always do this" would be rather simple to add.

    To initialize this, add an entry in ~/.eaglerc.  Perhaps something like:

     

        Dialog.OpenMatchingFile = {"Always","Never","Ask"}

     

    would work, with the absence of the line defaulting to "Ask"?  To revert

    the choice, all one would have to do is delete that line or set the

    value to "Ask" using a garden-variety plain text editor like vim or

    emacs (I'm a vim-guy myself).  By keeping this in ~/.eaglerc, it remains

    the choice of the user and does not affect others who might use the same

    installation.

     

    The fact that this thread boasts such a robust debate indicates that

    there is diversity of need.  As such, if I were on the design committee

    at CadSoft, I would at provide the user the choice and not mandate

    that the matching sch/brd always or never opens.  While there are

    clearly those who want to always open the matching file, there are also

    those want the option, and those who would choose "never".

     

    The task of predicting how one's software will be used is daunting to

    say the least.  The wider the customer base, the more configurable

    options have to be present, and documentation thereof, to accommodate

    unforeseen uses of the software.

     

    Enjoy,

        - Chuck

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • dukepro
    dukepro over 15 years ago

    On 02/25/2010 02:16 AM, Tilmann Reh wrote:

    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

     

    Alexander & Tilmann,

     

    All very good points.

     

    A checkbox in the dialog "Always do this" would be rather simple to add.

    To initialize this, add an entry in ~/.eaglerc.  Perhaps something like:

     

        Dialog.OpenMatchingFile = {"Always","Never","Ask"}

     

    would work, with the absence of the line defaulting to "Ask"?  To revert

    the choice, all one would have to do is delete that line or set the

    value to "Ask" using a garden-variety plain text editor like vim or

    emacs (I'm a vim-guy myself).  By keeping this in ~/.eaglerc, it remains

    the choice of the user and does not affect others who might use the same

    installation.

     

    The fact that this thread boasts such a robust debate indicates that

    there is diversity of need.  As such, if I were on the design committee

    at CadSoft, I would at provide the user the choice and not mandate

    that the matching sch/brd always or never opens.  While there are

    clearly those who want to always open the matching file, there are also

    those want the option, and those who would choose "never".

     

    The task of predicting how one's software will be used is daunting to

    say the least.  The wider the customer base, the more configurable

    options have to be present, and documentation thereof, to accommodate

    unforeseen uses of the software.

     

    Enjoy,

        - Chuck

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
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 © 2025 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