Melissa Appel is at it again on the SolidWorks Forums

Some time ago, Melissa Appel of SolidWorks started a thread in the SolidWorks forum for “silly” drawing workarounds.  This thread got a lot of attention.  Well, she’s at it again.  This time, she’s started a thread called “Show me what we can’t do in SolidWorks annotation formatting“.

There’s already a ton of suggestions that have been posted to this thread.  There’s a mention or two of bugs.  The notorious balloon quantity spacing issue is there.  Several issues with GD&T callouts are on the list.  Better control over breaks in extension lines, extension line termination and other dimensioning issues show up all over the thread.  I even suggested the creation of a SelectionWizard so that users can set up the order precedence when they want to select from several overlapping objects in SolidWorks drawings (and where the selection filter is not desired or is ineffective).

There’s plenty of room for more input in the thread for others who have ideas for improvement with annotation formatting in SolidWorks.  What’s been bugging you about SolidWorks annotation formatting limitations?

Author: fcsuper

As a drafter, mechanical designer and CAD engineer, I've been in the mechanical design field since 1991. For the first 8 years of my career, I was an AutoCAD professional. I utilized AutoLISP and many other AutoCAD customization features to streamline drafting activities for 6+ drafters and designers. I authored several custom functions, one of which was published in the March 1997 issue of Cadalyst Magazine. Since 1998, I've been used SolidWorks non-stop. I've worked to utilize the SolidWorks' user environment to simplify drafting and design activities for 20+ engineers. I've created this website to provide current information about SolidWorks from a variety of contributors. More recently, I am now employed by Dassault Systemes as SOLIDWORKS Sr. Product Definition Manager to improve drawing, annotation and MBD related areas.

Leave a Reply

Your email address will not be published. Required fields are marked *