Actions
Forum Thread Details
  • Replies 72 replies
  • Subscribers 180 subscribers
  • Views 7190 views
  • Users 0 members are here
Related

Open Sch & Brd files together

k.portman

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

 

Parents

  • Oliver Betz schrieb:

     

    The real old-fashioned user doesn't use the Eagle control panel to

    navigate to a project.

     

    The centralized organization introduces several years ago is not

    appropriate in many cases.

     

    Ack.

     

    For us, this means we must put the files into the EAGLE project

    directory for working on them, and don't forget to move them back into

    our project hierarchy afterwards.

     

    This also applies to many settings in the eaglerc file, e.g. the

    Directories.* entries - one might want to have different path settings

    for different projects. IMO these directories are no "user" settings

    but "project" settings. Well - many users will use the same

    directories for all projects, so it's convenient for them.

     

    ...but if there was a way to have them different between projects, it

    would satisfy both kinds of users.

     

    This could simply be solved by having the "user" settings as

    defaults which can be overridden by "project" settings.

     

    Tilmann

     

Reply

  • Oliver Betz schrieb:

     

    The real old-fashioned user doesn't use the Eagle control panel to

    navigate to a project.

     

    The centralized organization introduces several years ago is not

    appropriate in many cases.

     

    Ack.

     

    For us, this means we must put the files into the EAGLE project

    directory for working on them, and don't forget to move them back into

    our project hierarchy afterwards.

     

    This also applies to many settings in the eaglerc file, e.g. the

    Directories.* entries - one might want to have different path settings

    for different projects. IMO these directories are no "user" settings

    but "project" settings. Well - many users will use the same

    directories for all projects, so it's convenient for them.

     

    ...but if there was a way to have them different between projects, it

    would satisfy both kinds of users.

     

    This could simply be solved by having the "user" settings as

    defaults which can be overridden by "project" settings.

     

    Tilmann

     

Children
No Data