Tag Archives: Praise

AutoCAD 2018 – at last, something to praise

This isn’t supposed to be an Autodesk-bashing blog. Really, it’s not. Sure, Autodesk (and anyone else) gets criticism where deserved. There’s been a lot of that lately, but only because Autodesk has thoroughly deserved it. I don’t make up things so I can have a go; Autodesk provides the material all by itself.

Among other things, I’m a customer advocate. I don’t care who you are, act in an anti-customer manner and I’m going to slam you. Hard but fair. Dish up bullshit to your customers and I will gleefully point that out and heap derision on you. Deal with it.

On the other hand, act in a pro-customer manner and I’m going to praise you. I do praise Autodesk (and anyone else) where deserved. There are dozens of examples of that on this blog. Lately, the pickings have been slim. Time to redress the balance a little.

I’ve mentioned before that Autodesk has some great documentation people, including Lee Ambrosius

…who does a great job with developer documentation. That job’s less visible, but still very important and performed to an excellent standard. Lee is very technically knowledgeable and understands users, developers and their documentation requirements. Within the confines of the systems he’s forced to work with, Lee has done the very best job it would be possible for anyone to do.

Lee has again stepped up to the mark and done exemplary work with the AutoCAD 2018 developer documentation. See Lee’s post for details. This list of AutoLISP changes is an example of the sort of thoughtful addition Lee has provided. Thank you, Lee!

BricsCAD startup LISP bug fixed

In my previous post I have a real problem with BricsCAD, I related my then-latest interaction with the Bricsys support system:

Steve Johnson
05-12-2016 05:30 UTC

I don’t know if this is a BricsCAD problem or a DOSLib one, so I am reporting it to both Bricsys and Dale at McNeel. I’m also not sure if this was happening in earlier versions.

If I load DOSLib during an S::STARTUP call and then use the (dos_msgbox) function later in that call, this fails the first time round because BricsCAD things the function is not defined. Opening a second drawing results in the call working as expected. I’ve chopped down our startup routine so you have an example.

; error : no function definition ; expected FUNCTION at [eval]

Awesome Bricsys Person
05-12-2016 12:32 UTC

Hi Steve,

There was a regression introduced in V17.1.10 that caused startup code to execute too early under certain conditions, before the lisp engine document context was properly initialized. This has been fixed now for the next update.

Steve Johnson
06-12-2016 02:43 UTC

I must say, the responses I’ve been getting to my support requests have been absolutely bloody brilliant. Cheers!

Let’s just finish the sequence, shall we?

Second Excellent Bricsys Person
13-12-2016 19:18 UTC

Hi Steve,

I have very good news. The fix is included in BricsCAD V17.1.11, available for download.
Thank you for your help.

Following a fast and straightforward download and install, I can confirm that the bug is fixed. The elapsed time from my bug report to the fix being publicly available and me being informed personally of the fact was 8.5 days. Note that this isn’t a workaround, patch or service pack, it’s a permanent fix that is now automatically in place for everybody who downloads the software.

Edit: the new version was actually released at 4 PM on 9 December, so it was less than 4.5 days from report to fix. Outstanding!

I should mention that I also received a prompt and relevant response from Dale at McNeel, despite the fact that the problem was nothing to do with him!

For somebody used to dealing with Autodesk, this is a breath of fresh air. Bricsys team, take a bow!

Autodesk has some great documentation people

The most heavily commented post on this blog is AutoCAD 2013 – An Autodesk Help writer responds, featuring Dieter Schlaepfer‘s response to posts and comments here about AutoCAD 2013’s Help. I don’t always agree with Dieter but I respect him enormously, and not just because he was brave enough to stick his head above the parapet in a hostile environment. Dieter is a principal technical writer at Autodesk with many years’ experience and is therefore responsible for large amounts of documentation content. You’ve almost certainly read his work.

I’ve been critical of AutoCAD’s Help system since it was broken in 2011, and I make no apologies for that. The Help system sucked then, it sucked even worse in 2013, and it continues to suck badly in 2017. None of that’s Dieter’s fault. It’s the Help engine that’s at fault, or to be more accurate the Help engines, because the online and offline engines still both suck in various ways. Clearly there’s someone important at Autodesk satisfied with the ongoing Help engine awfulness, but that’s not Dieter. He’s responsible for content, not the engine. Content isn’t the problem. The content is actually very good, and gradually improving as Dieter finds ways to do so. It’s just that the system for accessing that content is so terrible that not many people get to read much of it these days, which is a crying shame.

I digress. Dieter’s awesome.

Also awesome is Lee Ambrosius, who does a great job with developer documentation. That job’s less visible, but still very important and performed to an excellent standard. Lee is very technically knowledgeable and understands users, developers and their documentation requirements. Within the confines of the systems he’s forced to work with, Lee has done the very best job it would be possible for anyone to do.

Everybody knows Lynn Allen, of course. Not just an entertaining and engaging presenter at AU and a thousand smaller gatherings, she has been producing beautifully prepared tips-and-tricks and what’s-new articles, posts and documents for so long she must surely have been a toddler when she started. The value of Lynn to Autodesk and its customers is hard to calculate, but is clearly immense.

Last but not least, Heidi Hewett has done an exemplary job for many years in producing preview guides, posts and other documents. You don’t get to see some of them because they are confined to pre-release testers, but I assure you that they are done to the same high standard as the ones that go public.

The work of our illustrious foursome and other talented writers can be found on the AutoCAD Blog and I’m sure my readers will find something of use there.