Project-specific configs - esp. drills, dimension

"Eric Deuel" <noreply-62020@element14.com> a écrit dans le message de news:

1009267270.10811336500410255.JavaMail.jive@flcspu-csapp-01.premierfarnell.com...

One thing that is quite bothersome is how the various parameters configurable under the

Options->Set menu are handled. It would really make sense for some of those parameters to be

project-specific,

You said "PROJECT oriented" ? see this topic:

http://www.eaglecentral.ca/forums/index.php?t=msg&th=46900&start=0&546e8117397602c11c874278d866e33a/

the Drills in particular. The drill table changes across projects so, when used in conjunction with

the drillegend-stack ULP (which requires the drills to be sorted by size), universally changing the

drill table gets cumbersome. This is particularly onerous when switching between multiple projects,

which I do frequently. Placing the drill table within the auspices of individual projects will keep

them proper.

The drill table is saved in the "eaglerc.usr" file. This is one of the reasons why I have to copy

this file in each of my project-directories.

I think that the drill table is specific for each board and should be saved in the board (as for

the DRC parameters).

One other related suggestion would be a Sort button in the drill table dialog.

This is a very old old old request :o(((

We could easily do that with an ULP but unfortunately the drill.symbol parameters as:

SET Drill.Symbol.Nr.4 = 0.8mm; doesn't works in the command line.

I use drillegend-stack ULP to generate the drill table for my fabricator. Having to go in a

manually sort the drill table is a manual task that should be readily automated.

Thanks for the insight.  After reading and implementing your suggestions from the linked topic, I discovered changing my HOME variable did bad things to other apps so had to change that back.  I've spent a bit more time looking at the various forum threads on the eaglerc.usr file and ran across the -U switch added to the command line options after Eagle v5.11.  Now my shortcut command line reads something like "eagle.exe -U.\eaglerc.usr" which points to the file local to the shortcut.  It is a bit of an annoyance to have to navigate to the project folder to launch Eagle rather than the pinned shortcut but it is a small price to pay.  I sincerely hope that this becomes easier in succeeding revisions - like defaulting to the .usr file in the project file if it exists before going to a global location like HOME.  Just a thought.

Thanks for the insight.  After reading and implementing your suggestions from the linked topic, I discovered changing my HOME variable did bad things to other apps so had to change that back.  I've spent a bit more time looking at the various forum threads on the eaglerc.usr file and ran across the -U switch added to the command line options after Eagle v5.11.  Now my shortcut command line reads something like "eagle.exe -U.\eaglerc.usr" which points to the file local to the shortcut.  It is a bit of an annoyance to have to navigate to the project folder to launch Eagle rather than the pinned shortcut but it is a small price to pay.  I sincerely hope that this becomes easier in succeeding revisions - like defaulting to the .usr file in the project file if it exists before going to a global location like HOME.  Just a thought.