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
  • autodeskguest
    autodeskguest over 15 years ago

    Travis G wrote on Thu, 25 February 2010 13:29

    A file manager is for viewing files, and whatever document creating

    software is for creating documents, and Eagle is for designing

    Electronics. I don't want a swiss army eagle.

     

    I totally agree.  I want CadSoft concentrating on making electronic design

    with Eagle better.  I already have plenty of other tools to help me write

    documents, edit firmware, etc.

     

    Quote:

    I don't know why some of you organize your files the way you do....

    Here's what I do and it works quite well:

     

    I do it even more stripped down in the Eagle directory.  Basically, I only

    keep Eagle stuff in the Eagle tree.  I keep my own eagle directory, which

    is separate from the Eagle installation directory.  The Eagle installation

    directory is only for stuff that comes from CadSoft.  All my own stuff goes

    into my own Eagle directory, and all the search paths for ULPs, libraries,

    etc, only look in my own eagle directory.

     

    One of my eagle subdirectories is "proj".  In there are directories for

    each separate customer.  Inside those are directories for each separate

    board.  I use a whole directory for each version of each board.  That way

    schematic, board, gerber, drill, drawing, BOM, and other files for a board

    are nicely in only one place and there isn't non-board stuff there

    cluttering things up.  There is rarely a nice one to one correspondence

    between boards, firmware versions, host programs, etc, so only

    board-related stuff goes into the board directories.  Firmware, host code,

    and documentation live other places in the system and have different

    organization.

     

    Only Eagle stuff lives in the eagle tree.  This makes the Eagle control

    panel actually useful for exactly what it was intended for.  I've never

    wanted to open a Eagle file other than thru Eagle.  CTRL-ALT-C (my own

    Windows hot key mapping) opens Eagle in a split second, then I can quickly

    and easily open whatever from there using the arrow keys and ENTER from the

    Eagle control panel.

     

    I think people would have a easier time with Eagle if they tried to embrace

    it for what it is and use other stuff for what it isn't.  There are way too

    many ways someone could set up their own workflow and structure, and it's

    not reasonable to ask Eagle to accomodate them.  Eagle does what it does

    well.  Fit it into your workflow as it was meant to be.  Don't try to

    modify Eagle to handle your workflow, because there will be a never ending

    list of things CadSoft would have to do to appease everyone once they start

    down this slippery slope.

    --

    Browser access to CadSoft Support Forums at http://www.eaglecentral.ca

     

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

    Travis G wrote on Thu, 25 February 2010 13:29

    A file manager is for viewing files, and whatever document creating

    software is for creating documents, and Eagle is for designing

    Electronics. I don't want a swiss army eagle.

     

    I totally agree.  I want CadSoft concentrating on making electronic design

    with Eagle better.  I already have plenty of other tools to help me write

    documents, edit firmware, etc.

     

    Quote:

    I don't know why some of you organize your files the way you do....

    Here's what I do and it works quite well:

     

    I do it even more stripped down in the Eagle directory.  Basically, I only

    keep Eagle stuff in the Eagle tree.  I keep my own eagle directory, which

    is separate from the Eagle installation directory.  The Eagle installation

    directory is only for stuff that comes from CadSoft.  All my own stuff goes

    into my own Eagle directory, and all the search paths for ULPs, libraries,

    etc, only look in my own eagle directory.

     

    One of my eagle subdirectories is "proj".  In there are directories for

    each separate customer.  Inside those are directories for each separate

    board.  I use a whole directory for each version of each board.  That way

    schematic, board, gerber, drill, drawing, BOM, and other files for a board

    are nicely in only one place and there isn't non-board stuff there

    cluttering things up.  There is rarely a nice one to one correspondence

    between boards, firmware versions, host programs, etc, so only

    board-related stuff goes into the board directories.  Firmware, host code,

    and documentation live other places in the system and have different

    organization.

     

    Only Eagle stuff lives in the eagle tree.  This makes the Eagle control

    panel actually useful for exactly what it was intended for.  I've never

    wanted to open a Eagle file other than thru Eagle.  CTRL-ALT-C (my own

    Windows hot key mapping) opens Eagle in a split second, then I can quickly

    and easily open whatever from there using the arrow keys and ENTER from the

    Eagle control panel.

     

    I think people would have a easier time with Eagle if they tried to embrace

    it for what it is and use other stuff for what it isn't.  There are way too

    many ways someone could set up their own workflow and structure, and it's

    not reasonable to ask Eagle to accomodate them.  Eagle does what it does

    well.  Fit it into your workflow as it was meant to be.  Don't try to

    modify Eagle to handle your workflow, because there will be a never ending

    list of things CadSoft would have to do to appease everyone once they start

    down this slippery slope.

    --

    Browser access to CadSoft Support Forums at http://www.eaglecentral.ca

     

    • 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