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
    About the element14 Community
  • 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 Chat (English) Out of the Box Gripes
  • 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 24 replies
  • Subscribers 189 subscribers
  • Views 1685 views
  • Users 0 members are here
Related

Out of the Box Gripes

autodeskguest
autodeskguest over 16 years ago

Hello everyone,

 

EAGLE is quite powerful and flexible.  But with great flexibility comes

great irritation if you don't know how to do it (or even that you can).

And new users may either get discouraged and leave the community, work

inefficiently for years and not realise it, or even worse, not realise an

easy to fix issue and get back boards that don't work (thinking of cam job

mirroring of bottom layer).

 

So what is on your list of things that EAGLE could configure better out of

the box.  I'm not talking about any new functionality.  I'm thinking about

things that EAGLE will do, but is just not configured out of the box.  Or

things that everyone does the first time they install EAGLE.

 

Here's a start, please add to it.  This is meant to make EAGLE even better,

not just annoy people, so try to be constructive image  Hopefully the new

people at Newark will take this list seriously as it greatly effects that

first impression new users get.  A bad one and they might never come back.

 

1)  bill of materials and x-y data generation integrated, documented, and

supported.

 

2)  advanced find integrated, documented, and supported

 

3)  better use of colour pallette and default values other than indices

16-63 being gray (or grey if you like)

 

4)  default CAM jobs mirror bottom layer, shouldn't be done normally

 

5)  key assignments for all normal activities, documented and supported.

Of course, users can make their own changes by editing eagle.scr etc, but

again most users don't really know that is possible.  And a template

document that you can edit to give new employees the cheat sheet.

 

That's a start, I'm sure there are a ton more.

 

Cheers,

 

James.

--

James Morrison  ~~~  Stratford Digital

 

email:  james@eaglecentral.ca

web: http://www.eaglecentral.ca

 

Specialising in CadSoft EAGLE

  • Online Sales to North America

  • Electronic Design Services

  • EAGLE Enterprise Toolkit

--

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

 

  • Sign in to reply
  • Cancel
Parents
  • e14 Contributor
    e14 Contributor over 16 years ago

     

    "James Morrison" <james@eaglecentral.ca> wrote in message

    news:hhj6ri$urt$1@cheetah.cadsoft.de...

    Hello everyone,

     

    EAGLE is quite powerful and flexible.  But with great flexibility comes

    great irritation if you don't know how to do it (or even that you can).

    And new users may either get discouraged and leave the community, work

    inefficiently for years and not realise it, or even worse, not realise an

    easy to fix issue and get back boards that don't work (thinking of cam job

    mirroring of bottom layer).

     

    So what is on your list of things that EAGLE could configure better out of

    the box.  I'm not talking about any new functionality.  I'm thinking about

    things that EAGLE will do, but is just not configured out of the box.  Or

    things that everyone does the first time they install EAGLE.

     

    Here's a start, please add to it.  This is meant to make EAGLE even

    better,

    not just annoy people, so try to be constructive image  Hopefully the new

    people at Newark will take this list seriously as it greatly effects that

    first impression new users get.  A bad one and they might never come back.

     

    1)  bill of materials and x-y data generation integrated, documented, and

    supported.

     

    2)  advanced find integrated, documented, and supported

     

    3)  better use of colour pallette and default values other than indices

    16-63 being gray (or grey if you like)

     

    4)  default CAM jobs mirror bottom layer, shouldn't be done normally

     

    5)  key assignments for all normal activities, documented and supported.

    Of course, users can make their own changes by editing eagle.scr etc, but

    again most users don't really know that is possible.  And a template

    document that you can edit to give new employees the cheat sheet.

     

    That's a start, I'm sure there are a ton more.

     

    Cheers,

     

    James.

    --

    James Morrison  ~~~  Stratford Digital

     

    email:  james@eaglecentral.ca

    web: http://www.eaglecentral.ca

     

    Specialising in CadSoft EAGLE

    • Online Sales to North America

    • Electronic Design Services

    • EAGLE Enterprise Toolkit

    --

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

     

     

     

    Hello James,

     

    I am listing some of the sames 'gripes' as have been listed already, but

    just wanted to give some input about what I experience with customers.

     

    *Vector font output - confusion about being about to design with

    proportional or fixed font, but only outputs vector.

    *CAM jobs mirroring bottom side layers by default.

    *Stacked pad issue - When the name of the layer contains the $ character,

    pads and vias need to be deselected during output.  If not, it creates a pad

    and clearance in the same spot.

     

    As far as documentation, it may not be a bad idea to have a list of errors

    (with screenshots) and some explanation on how to resolve the issue.  For

    example, 'Invalid Polygon' error for files created in older versions of

    EAGLE; 5.0 now recognizes the invalid polygons, while older versions do not.

    And another off the top of my head, 'Polygon may cause extremely large plot

    data'... when the polygon width is too small.  There are more, but these

    come to mind right now.

     

    I know that the answers can be found in the documentation and/or help menu,

    but having the list would save tons of time on searching and hoping that the

    search terms that you are using are correct.

     

    That's all I have for now!

     

    Best regards,

     

    Terri

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • e14 Contributor
    e14 Contributor over 16 years ago

     

    "James Morrison" <james@eaglecentral.ca> wrote in message

    news:hhj6ri$urt$1@cheetah.cadsoft.de...

    Hello everyone,

     

    EAGLE is quite powerful and flexible.  But with great flexibility comes

    great irritation if you don't know how to do it (or even that you can).

    And new users may either get discouraged and leave the community, work

    inefficiently for years and not realise it, or even worse, not realise an

    easy to fix issue and get back boards that don't work (thinking of cam job

    mirroring of bottom layer).

     

    So what is on your list of things that EAGLE could configure better out of

    the box.  I'm not talking about any new functionality.  I'm thinking about

    things that EAGLE will do, but is just not configured out of the box.  Or

    things that everyone does the first time they install EAGLE.

     

    Here's a start, please add to it.  This is meant to make EAGLE even

    better,

    not just annoy people, so try to be constructive image  Hopefully the new

    people at Newark will take this list seriously as it greatly effects that

    first impression new users get.  A bad one and they might never come back.

     

    1)  bill of materials and x-y data generation integrated, documented, and

    supported.

     

    2)  advanced find integrated, documented, and supported

     

    3)  better use of colour pallette and default values other than indices

    16-63 being gray (or grey if you like)

     

    4)  default CAM jobs mirror bottom layer, shouldn't be done normally

     

    5)  key assignments for all normal activities, documented and supported.

    Of course, users can make their own changes by editing eagle.scr etc, but

    again most users don't really know that is possible.  And a template

    document that you can edit to give new employees the cheat sheet.

     

    That's a start, I'm sure there are a ton more.

     

    Cheers,

     

    James.

    --

    James Morrison  ~~~  Stratford Digital

     

    email:  james@eaglecentral.ca

    web: http://www.eaglecentral.ca

     

    Specialising in CadSoft EAGLE

    • Online Sales to North America

    • Electronic Design Services

    • EAGLE Enterprise Toolkit

    --

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

     

     

     

    Hello James,

     

    I am listing some of the sames 'gripes' as have been listed already, but

    just wanted to give some input about what I experience with customers.

     

    *Vector font output - confusion about being about to design with

    proportional or fixed font, but only outputs vector.

    *CAM jobs mirroring bottom side layers by default.

    *Stacked pad issue - When the name of the layer contains the $ character,

    pads and vias need to be deselected during output.  If not, it creates a pad

    and clearance in the same spot.

     

    As far as documentation, it may not be a bad idea to have a list of errors

    (with screenshots) and some explanation on how to resolve the issue.  For

    example, 'Invalid Polygon' error for files created in older versions of

    EAGLE; 5.0 now recognizes the invalid polygons, while older versions do not.

    And another off the top of my head, 'Polygon may cause extremely large plot

    data'... when the polygon width is too small.  There are more, but these

    come to mind right now.

     

    I know that the answers can be found in the documentation and/or help menu,

    but having the list would save tons of time on searching and hoping that the

    search terms that you are using are correct.

     

    That's all I have for now!

     

    Best regards,

     

    Terri

     

     

     

    • 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 © 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.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube