Tag: <span>R.K. McSwain</span>

CAD Panacea tip – startup files in BricsCAD

One of the things that might initially baffle a CAD Manager or power user when investigating switching from AutoCAD to BricsCAD is how to set up the startup routines. Head over to CAD Panacea for R.K. McSwain’s concise, handy description of how to do it. Due to BricsCAD’s high level of compatibility, you can maintain a common folder or set of folders containing LISP and other custom files for both applications. That way, you don’t need to do double maintenance during the transition period. I’ve done this successfully in a highly complex custom environment. Some code and other adjustments were …

CAD-related Twitter exchange of the year

In a Twitter post (now deleted), the AutoCAD twitter account asks us to submit our feature ideas for AutoCAD, and links to the Autodesk Ideas Page: Just one problem. As R.K. McSwain points out in his reply, the Ideas Page has no section for AutoCAD. There should be one, and should have been one for years, but there isn’t. That tells you all you need to know about how the level of concern Autodesk has about AutoCAD’s future development. Here’s the exchange in all its glory: Oops.

The big Bricsys interview 10 – platforms

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh. In this post, R.K. McSwain asks about BricsCAD running on three different platforms. Erik explains why BricsCAD for Mac (and Linux) is so much more complete than AutoCAD for Mac, which has more holes than a block of Swiss cheese. R.K.: Do all three platforms (Windows, Linux, Mac) contain the same functionality? Erik: Yes. Sometimes it’s a bit hard with the Mac to bring it along but so far, so good. The only problem sometimes is …