Hotfix for AutoCAD 2017 SP1 Autoloader bug

As reported earlier, AutoCAD 2017 SP1 breaks third-party add-ins that use the officially approved Autoloader mechanism. Autodesk is to be commended for acting quickly to produce a hotfix for this. In order to make this hotfix available quickly, Autodesk has taken the very unusual step of allowing a third party to distribute it. See this post from Jimmy Bergmark, who pointed out the bug in the first place. Kudos to whoever at Autodesk made the call to think outside the box to do this. It’s a very un-Autodesk Corporate thing to do, and particularly commendable for … Full post

AutoCAD 2017 Service Pack 1 is out but you probably don’t want to install it

As reported by Jimmy Bergmark, AutoCAD 2017 SP1 will break add-ins that use Autodesk’s built-in autoloader mechanism. It looks like it’s a problem caused by third party applications, but it’s not. It’s entirely Autodesk’s fault. The only fix at this stage is to uninstall SP1.

It’s astonishing that Autodesk would release a service pack like this, introducing a nasty bug that will break customers’ existing functionality. This reminds me of the comedy of errors that was AutoCAD Release 13 with its multitude of updates, many of which introduced new bugs as well as fixing others. AutoCAD 2017c4a, … Full post

Shout out to Robert McNeel & Associates

Let’s start the rebirth of this blog on a positive note. I’d like to express my gratitude to Robert McNeel & Associates for what must surely be the most outstanding example of long-term customer service in the CAD industry.

These days, McNeel is best known for the 3D modelling software Rhino. I have heard good things about this product, but have never used it. However, I am a long-term user of another McNeel product, DOSLib. This is an extensive set of functions that adds greatly to the functionality of AutoLISP. It all works very well … Full post

AutoCAD 2013 Help shock – it no longer sucks

Some months ago, I gave Autodesk several damn good (and thoroughly well-deserved) thrashings over its hopelessly inadequate AutoCAD 2013 Help system. When Autodesk’s Dieter Schlaepfer responded and asked for feedback, he sure got it. There are 142 comments on that one post to date, most of them leaving nobody under any illusions about how short of the mark the new system was.

There is now an updated version of the AutoCAD 2013 Help system. It has been an interminably long time coming, a fact made far worse by Autodesk’s stubborn … Full post

LISP programmers, have your say again

Autodesk wants your input again in its annual API survey. This used to be a closed survey for Autodesk Developer Network (ADN) members, but has been open to all for the last few years. If you do any AutoCAD-based development at all, I encourage you to take part. That includes those of us who do most of our development in LISP.

Here’s the direct link to the survey. As you can see if you click the link, there’s a lot of stuff in there that assumes you’re keen to get developing for AutoCAD WS. If you’re … Full post

AutoCAD 2013 – Using Help in anger

Trying to be fair, I decided to put aside my initial hostility to the AutoCAD 2013 Help system and use it for real. I used it in a realistic situation, to find out how to work with something new or changed (model documentation) as I was working through it with my own example drawing. Try as I might to give it a fair go, I could only get so far before I got irritated. Using it in anger might not be an entirely appropriate phrase for it, but it’s not that far off. Using it in annoyance, perhaps? Here’s how it went.

I … Full post

AutoCAD 2013 – Help improved in one area

There’s one important area in which AutoCAD 2013’s Help shines when compared with its immediate predecessors. If you’re a Visual LISP user, you’ll be pleased to know that if you select a function name in the editor (e.g. (vla-get-ActiveDocument)) and hit Ctrl+F1, this now takes you to the appropriate page in the ActiveX and VBA Reference, as it should. In AutoCAD 2011 you just got a cryptic message or a 404 error, depending on the context. In AutoCAD 2012, you were just taken to the front page of Help and expected to find it yourself. Props to Autodesk for fixing … Full post

Autodesk’s Kean about moving to the Cloud

Autodesk’s API guru Kean Walmsley is the second Autodesk person I’ve seen who has been brave enough to stick his head above the parapet by discussing the Cloud, in writing, and in a medium that allows for public comment. Kean has always seemed like a straight shooter to me. Please note that his blog represents his personal opinions rather than an official Autodesk position. He’s after your comments, so please go and let him know what you think on his post. Add your comments here if you’re more comfortable with that, and I’ll make sure Kean … Full post

The worst feature ever added to AutoCAD is…

…the Ribbon, according to your selections in the What are the worst features ever added to AutoCAD? poll. As in the best ever poll, the winner (loser?) in this race had no serious competition. I’ve listed eleven top (bottom?) features here rather than ten, partly because the popular (unpopular?) choice Memory Overuse isn’t exactly a feature. But it’s mainly because I’d hate to see Action Recorder unfairly miss out on a well-deserved mention.

  • Ribbon (30%)
  • CUI (20%)
  • Help (on line / 2012) (18%)
  • Memory Overuse (17%)
  • AutoCAD Today (2000i/2002) (16%)
  • White / Cream Drawing Background (16%)
  • Full post

(so (long (and (thanks (for (all (the (parentheses))))))))

A few days ago, John McCarthy died at the age of 84. He didn’t make a fortune selling gadgets, he just profoundly affected the world of computing. He will be remembered mainly as the father of LISP, without which it is quite possible that AutoCAD and Autodesk would not have survived beyond the 80s. However, his original thinking went well beyond the development of a language. For example, 50 years ago he came up with an idea that is very relevant to what we are actively discussing today:

In 1961, he was the first to publicly suggest (in … Full post

Taking control of your command line history

Thanks to Kean Walmsley’s post on his Through the Interface blog, I have learned something that would have been handy to know for the last decade or so, but which somehow escaped my knowledge. I learned how to increase the size of AutoCAD’s command line history cache. It defaults to 400 lines, which isn’t enough for me. I think this information deserves a wider audience than the ubergeek developers who frequent Kean’s blog, so here goes.

Although it’s not directly mentioned on Kean’s post, you can find the current command line history cache length setting like … Full post

Old news – shipping version of ClassicArray released

I have been somewhat neglectful of this blog lately, including a failure to mention that my ClassicArray™ plug-in for AutoCAD 2012 has been shipping since 1 May 2011. Thank you to those people from various places around the world who have been prepared to go to the effort of registering and paying for the product.

Here are some details of the product taken from the ClassicArray page:

ClassicArray is a simple-to use but powerful tool for creating arrays in AutoCAD.

  • Provides a dialog box interface to AutoCAD 2012’s Array command. The familiar interface … Full post

AutoCAD 2012 – Autoloader mechanism for plug-ins

One of the less obvious features introduced by AutoCAD 2012 is the Autoloader mechanism that has been provided to make installation of plug-ins (current standard Autodeskspeak for add-ons, apps, utilities, routines, etc.) easier for both developers and users. It may not be immediately obvious, but it’s a useful and important addition.

This mechanism has nothing to do with the AppLoad command, the Startup Suite, acad*.lsp, the (autoload) function or anything else that existed in earlier releases. This is completely new, it has not replaced or broken any of the existing loading mechanisms, and is, in short, A Good Thing. Developers … Full post

ClassicArray Release Candidate 2

I have now posted the second Release Candidate of ClassicArray™ (version number 0.7.0). The main changes from the first Release Candidate (0.6.0) are:

  • Help documentation, which you can also view here, now describes how to resolve an AutoCAD CUIx loading problem. (The problem is not specific to ClassicArray and can affect any CUIx file that is removed or relocated. More on that in a future blog post).
  • Timebomb mechanism now works 15 days after first use rather than a specific date. Also now allows the interface to still be used (but no arrays to be created) once the … Full post

ClassicArray Release Candidate – massive download bloat

I have just posted the Release Candidate of ClassicArray™ (version number 0.6.0). The main changes from Beta 2 (0.5.0) are:

  • Setup executables have been provided to provide easier installation and uninstallation.
  • Pretty comprehensive Help documentation is now in place, which you can also view here if you want to learn about the product without installing it.
  • Bug fixed with Path preview not displaying accurately when no path is selected.
  • Minor cosmetic dialog box fixes.
  • Timebomb has been moved on 7 days to 28 April.

Regrettably, the download file size has blown out to 787 KB because of … Full post

ClassicArray pricing proposal

I am considering the following pricing model for ClassicArray™ when it’s released:

Individual licenses: $12
Up to 20-user license: $100
Up to 50-user license: $200
Up to 100-user license: $300
Unlimited site license: $500

Prices in US$, payment by PayPal, delivery by download only. Australian purchasers would have to pay 10% GST on top of that.

Comments? Suggestions?

ClassicArray Beta 2 (0.5.0)

I have just posted the second public Beta of ClassicArray™ (version number 0.5.0). There are some documentation updates (still no Help, though), and the main changes are:

  • Bugs fixed with rectangular arrays where single-row and/or column arrays confused AutoCAD.
  • The command now remembers its settings from one invocation to the next, within a single drawing session.
  • Timebomb has been moved on 7 days to 21 April.

The ReadMe.txt file in the zip explains how to uninstall the old version. Simply delete the old ClassicArray.bundle folder from the place you put it. Replace it with the new ClassicArray.bundle folder … Full post

AutoCAD 2012 – ClassicArray Beta

People have already started to notice that AutoCAD 2012 has killed the dialog box interface for the Array command, and not everybody is happy about it. So I guess it’s time to launch ClassicArray™ Beta.

ClassicArray is an add-on for AutoCAD 2012 for Windows that allows the creation of arrays using a dialog box interface similar to that provided in AutoCAD from 2000 to 2011, but enhanced to include new AutoCAD 2012 functionality. I will create another post later have created a Help page that describes ClassicArray more fully, but for now here are the commands ClassicArray adds … Full post

Autodesk for Mac – the hole story

You may remember my pre-release speculation about what was likely to be missing from the Mac version of AutoCAD 2011. It turns out that my list was pretty accurate as far as it went, but very incomplete.

In a move that I can only applaud, Autodesk has now published its own list of missing Mac features. It includes this statement:

Although AutoCAD 2011 for Mac is based on AutoCAD 2011, it was written to be a native Mac application. As such, it is a new and separate product and not simply a port from the Windows version. In … Full post

Executive summary of Deelip’s AutoCAD for Mac interview

Deelip has just published an extensive interview with several Autodesk people about AutoCAD for the Mac. Deelip had a good set of questions and I suggest you read the whole thing, but if it’s all too tl;dr for you, then here is the lazy reader’s version of what Autodesk had to say:

  • The AutoCAD code was split up into 3 sections: the core CAD engine (platform-independent), the Windows-specific (MFC) parts and the Mac-specific (Cocoa) ones.
  • AutoCAD for Mac is incomplete. Choosing which features to leave out was done with the aid of CIP (oh, dear) … Full post