Sometimes users want to capture AutoCAD command line output for parsing into a report.  The quick easy way if you don’t have too much content is right clicking the command line area, choosing Copy History and pasting that into an editor to remove the unnecessary parts.  However sometimes your content exceeds the history buffer or you just want more control.

AutoCAD LOG controls allow you capture what you want, here are the details.

Read More →

We have reached a fork in the road on our Civil/Survey and Mapping add-ons.  For years we attempted to provide one package that ran inside plain CAD engines as well as Civil3D while using the best objects available.   The problem is that it meant a weaker (than possible) Civil3D connection, prevented us from adding tools only (currently) possible in Civil3D and created confusion on what parts used Civil3D objects.

Read More →

We are occasionally asked why our products don’t directly import point ascii files.

Keep in mind that TXT/ASC files can contain anything (even the paragraphs of this post content) so we process it differently.  We have a Point > File > Convert Text which handles any text file, regardless of the delimiter.  It lets you preview the content, specify the delimiter and column order then parse the results into a defined point format.

If your ascii files are P,N,E,Z,D you can simply change the extension to .AUF and the program would read the files directly.

Recent versions of AutoCAD change the default behavior of newly created Mtext objects.  After creation you can’t change the Width in the Properties dialog!  Users often want to set the width to 0.0.

For existing Mtext objects, change the Columns setting (just below the width) to “No Columns”.  You will have to commit this change by pressing ESC, then reselect the Mtext to be able to change the width.

To restore previous behavior for all newly created Mtext, change the MTEXTCOLUMN to 0 in your current (and prototype) drawing.