I’ve added a link to Without A Net, a new blog on support issues, technical solutions, fixes, and tips for AutoCAD. It’s run by Tom Stoeckel, global technical lead for AutoCAD product support. In my limited experience, I’ve found Tom to be a fine fellow with his customers’ needs at heart. This blog promises to be a worthwhile addition to the existing AutoCAD support mechanisms, and I commend Autodesk and Tom for introducing it.
I generally avoid the still-awful Autodesk discussion groups these days, but I do hop in from time to time in the vain hope of seeing some improvement. In doing so, I occasionally pick up a gem, and that happened today. I think this one deserves a wider audience, so here it is.
In AutoCAD 2010, you can disable the InfoCenter toolbar by opening the
registry, and going to the following key:HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R18.0\ACAD-8001:409\InfoCenter
In that key there’s a value with the name “InfoCenterOn”.
Changing that value from 1 to 0 will disable the InfoCenter toolbar.
Source: Tony Tanzillo in this thread. Note that the “ACAD-8001” part will be different if you use a vertical variant of AutoCAD.
Why would you want to do this? To improve startup times and reduce annoyance. Autodesk should have provided a better mechanism for doing this. The absence of convenient, designed-in off switches for new features is something I’ve complained about on many occasions over the years. Autodesk’s response has been patchy.
Edit: I just noticed Owen Wengerd has posted about this, including a LISP routine to simplify the process of turning it on and off.
I’ve added a link to Autodesk’s new AutoCAD community site, AutoCAD Exchange. As with most things Autodesk, there are pros and cons. Here are my first impressions.
I think it looks good in a Vista-black kind of way. I know some of you don’t like the black look in software, but I do. The layout looks a bit cluttered and confused at first, but I’m sure visitors will quickly get used to where to find things. The site appears to be designed around 1024-wide resolution. If you have more than this, as most CAD users do, then there are wide areas of wasted space either side of the good stuff.
The front page is basically a teaser. To get to the useful content or do pretty much anything, you need to register or sign in. I don’t particularly like this, and it gives the impression (false or not) that Autodesk wants to own and control you, even if you’re just viewing a site. The registration process is the same as for other Autodesk sites such as the discussion groups, so if you have an Autodesk identity, you’re already registered.
As it is a “community” site, on first sign-in you are invited to fill in more details, provide an avatar and so on. Some people might not like this, but it’s optional and Autodesk knows where I live so it makes no difference to me. I know where Autodesk lives, too. It has yet to be seen if Autodesk manages to develop a real community on this site, and if so, how open that community is allowed to be.
Autodesk is encouraging bloggers to add an Autodesk Exchange widget to their blogs. I won’t be adding one in a permanent position because this is my blog and not Autodesk’s. I kind of like my independence, and if a company wants space on my blog they can pay for it. Anyway, the widget is available in three sizes and here’s what the largest one looks like:
I’m likely to appear in one of those little interview videos soon, as they were shot during the bloggers’ visit to San Fransisco in early February. When you do get to see it, yes, that’s really me (and Melanie Perry) saying nice things about AutoCAD 2010, it’s not computer generated. Except for the background, that is, which is computer generated. It was bright green in real life. Other than that, no deception, lies, arm-twisting or bribes were involved. Oh, unless you count the free trip to San Fransisco as a bribe. I interviewed Autodesk, they interviewed me, and I actually had positive things to say about AutoCAD 2010. More on that later.
AutoCAD Exchange is an important and potentially very useful site for AutoCAD users. Check it out, and if you feel like it, report back. You can pretty much say what you like here.
The final question is from metis:
Q: why is program size increasing and performance dramatically decreasing as hardware specs dramatically increase? as features “improve” and are added functionality should not be removed, and code should be streamlined.
seriously aren’t there any real programmers out there anymore? this thing isn’t written in java by a bunch of scriptkiddies (although 2009 sure is skinned like it was).
A: We made a number of performance improvements in AutoCAD 2010 over the previous release, and would appreciate hearing from you if you are encountering significant performance slowdowns with this latest release. If so, please send us details on what you were doing at the time, sample files if possible, and details on the machine you are using. This will help us improve performance further in upcoming releases of AutoCAD.
The third question, courtesy of Earl Kubaskie, is:
Q: I would ask why there seems to be so little cooperation between the development teams. Vanilla, Map 3D, Civil 3D, each seem to be separate little empires. ACA might be in there, too, but I don’t use it, and thus I don’t apply for the betas.
I would think that closer interaction (and consolidation of beta testing teams) would smooth out the process – and maybe help get Matt his wish re bonus packs.
A: This is an ongoing area of focus for us, and this year we are making further changes that we believe will help bring the AutoCAD family of products closer together. In this release you’ll see consistency between the user interface as well as some of the new features, such as hatch enhancements, that behave similarly across AutoCAD products.
In a comment on the first of these posts, Ralph G raised the possibility that these answers have been edited by marketing people. I have checked with Eric Stover and he assures me these answers come direct from the program managers concerned and are unmassaged by marketers. That ties in with the partial email trail that came with the answers. It also ties in with the impression I have formed recently that Autodesk is starting to open up a bit. That’s a trend I’m happy to encourage.
There’s one thing that clinches the marketing-interference matter for me. Despite Eric being on vacation when I sent in the request, the answers came back in days rather than weeks or months.
Enough of that, here’s the next question, courtesy of Matt Stachoni:
Q: Why haven’t the latest Subscription Bonus Packs been released for AutoCAD Architecture Subscription customers?
A: This year was the first time we released bonus packs continuously throughout the year to AutoCAD subscription customers, and we had a lot to learn about how to best deliver the bonus packs, and how often to release them. Based on our learnings from this year, our plan for the coming year is to ensure that AutoCAD Architecture (and other AutoCAD vertical product) subscription customers also receive any AutoCAD updates and bonus packs we deliver.
At the end of January, I asked for your questions to put to Autodesk product managers. My intention was to pose your questions in a video interview format while attending the AutoCAD 2010 product launch, but for logistical reasons I was unable to make this happen.
Autodesk’s Eric Stover kindly arranged for your questions to be answered anyway. The delay in getting these answers back to you is my responsibility, not Autodesk’s. The answers come courtesy of the following product managers:
I will post each question and answer a day apart, to give you chance to comment on each issue separately. Here is the first question, courtesy of Chris Cowgill:
Q: With the current release cycle being so short, has anyone considered suspending a new release for a time, to spend an entire release cycle working on improving/restoring functionality of existing features and fixing bugs, why, or why not?
A: With any given release, we aim to deliver a healthy balance of new features & functionality along with improvements to existing functionality, so we can help enable new ways of doing design, but also provide more efficient ways of working the way you do today. We plan to continue this balancing act for future releases, but have also started delivering regular product updates (formerly known as ‘service packs’) throughout the year. So, rather than requiring you to wait for a new release of the product to get product improvements, this year we delivered 3 product updates that included hundreds of bug fixes to existing AutoCAD features and functionality.
I know there are plenty of people still using AutoCAD 2007 and earlier, so this bug warning may save some of you some grief. I have no idea how widespread or isolated this problem is, but under some circumstances I haven’t worked out yet, AutoCAD 2007 fails to plot all of certain dynamic blocks. Some attributes have a habit of being plot-shy. Even if you don’t use dynamic blocks yourself, you could receive a set of drawings, check them on-screen, approve them, plot them and send out paper drawings without all of their parts. Unless you’re carefully manually checking the paper plots, this situation is obviously a little dangerous. Fortunately, Plot Preview also shows up the problem, so it is at least possible to check things without wasting trees.
Here’s an example. This is part of such a drawing displayed in AutoCAD 2007, with all of its parts in place. One of the dynamic blocks is highlighted:
Here’s that drawing plotted using AutoCAD 2007, showing the missing parts:
Earlier releases do the same, including pre-dynamic block releases. As DWF files are just electronic plots, the same problem applies to them. Yes, I’ve checked for non-plotting layers and looked into the visibility states within the dynamic blocks. An audit of the drawing indicates no problems. Attribute visibility settings are not an issue.
Here’s the same drawing plotted using AutoCAD 2009 (2008 and 2010 are fine, too):
What to do? Using a later release would solve it, but might not be a practicable solution in your office right now. Instead, you could consider using DWG TrueView for your plotting. That may not be ideal either, but it could be better than risking the consequences of an unknown number of your plots containing an unknown number of missing parts in unknown places.
Have you come across this problem? If you have any more clues about the circumstances that trigger it, please add a comment.
I’ve closed the poll that asked AutoCAD 2009 users about their MENUBAR setting. It’s very clear that pull-down menus are still very much in use in the Ribboned world of post-2008 AutoCAD. In AutoCAD 2009, an attempt was made to provide access to pull-down menus without sacrificing that strip of screen real estate. That attempt was called the Menu Browser, it was one of the thing you could find under the Big Red A, and it really didn’t work very well. In AutoCAD 2010, the Menu Browser has gone away. The A hasn’t gone away, just the ability to access pull-down menus through it.
There are some who have expressed a deep dislike of the Big Red A, although it never offended me greatly. I just wished the features hidden under it worked better than they did in 2009. Personally, I generally prefer what’s under the A in 2010 than what’s there in 2009, but you may not. I know that when the 2009 user interface was being attacked, its most prominent defenders were those keyboard-heavy users who turned both the Ribbon and the menu bar off, giving themselves more screen space. On the infrequent occasions when a pull-down menu was required, those people were content to provide an extra click.
When I found out about the Menu Browser’s death a few months ago, I expected there would be a severe adverse reaction from such people. Maybe there will be one when people hold get the shipping product and notice it’s gone. But after my poll showed only 7% of respondents used it instead of the menu bar, I’m now expecting that adverse reaction to be smaller than I originally thought.
If you want to use AutoCAD 2010, want to work without a menu bar but still have access to menu items occasionally, what can you do? You can add a button to the Quick Access Toolbar (QAT), or any other toolbar, that toggles the menu bar on and off. Use the CUI command to add such a button.* The following macro will do the job:
'menubar $M=$(-,1,$(getvar,menubar))
There are a couple of downsides to this method. First, although this macro has been written in such a way that it should be transparent, it doesn’t currently work that way. When you push the button, AutoCAD will still cancel any command you’re in. Second, the screen resize forces a redraw, which could slow you down in very complex drawings. However, under most circumstances that redraw will still be quicker than waiting for a reaction from AutoCAD the first time you pick the Big Red A. By the way, that reaction time is better in 2010 than the very tardy 2009. As a result, even AutoCAD 2009 users might prefer to use the QAT-button method and forget the Menu Browser ever existed.
* If there is enough interest, I will do a video tutorial explaining how to add such a button to the QAT.
If you had a real live Autodesk development person standing in front of you right now (an AutoCAD Product Manager, for example) and were allowed to ask one question, what would it be?
Please add a comment here with your question. I would ask that you keep your question civil and reasonably concise (one or two sentences), and bear in mind that the development person in front of you isn’t going to have a useful answer to policy questions about pricing, license agreements, customer service and so on. Other than that, anything goes, so let’s have ’em.
I can’t promise that your question will get answered, but I’ll see what I can do.
Note: comments are now closed, as this post keeps getting mistaken for an ongoing mechanism for asking Autodesk questions.
Although I want to keep my list of links reasonably compact, it should not have taken until now to add the AutoCAD Insider blog of Autodesk’s Heidi Hewett to the list. Heidi’s idea of going through the AutoCAD alphabet is a great one, and I wish I had thought of it.
blog nauseam has been light on for AutoCAD tips and information lately. Although that’s going to change for the better soon, there’s plenty of that kind of stuff on Heidi’s blog to keep you amused in the meantime. It’s useful stuff for all AutoCAD users, explained well.
Oh, and Heidi, the Boundary command was (kind of) added in Release 12, except it was called Bpoly at the time. It was renamed to Boundary in Release 13. The Bpoly command lives on to this day, doing exactly the same as Boundary.
You may have noticed that I’ve added a poll to find out if the AutoCAD 2009 users among you are using the menu bar (i.e. MENUBAR = 1). I’m also interested in hearing your comments about your usage and the reasons behind it.
If your menu bar turned on, why? Do you use it all the time or do you just need it for those less-frequently-used commands that you don’t have handy at your fingertips, on toolbars, palettes or the Ribbon? Do you need it because your own custom routines are on menus, or third-party commands? Does the vertical AutoCAD variant you’re using need it?
If your menu bar is turned off, why? Do you never have any need for the stuff in there? Do you use the Menu Browser instead, sacrificing an occasional extra click for the sake of a permanent strip of screen space?
I’ve now closed the poll that asks this question, and the results show a typical bell-curve shape with the peak clearly on “Half-baked”. There is a slight bias to the bottom end, but not a significant one.
This result doesn’t surprise me, as I’ve seen and heard a lot of user comments to that effect, and I’ve made such comments myself. I’m not saying that this poll is definitive proof of anything, but it sits pretty well with my perception of what AutoCAD users generally think.
Now I’d like you to consider a related question. If we accept for the sake of argument that the average major new AutoCAD feature is half-baked, is that necessarily a bad thing? There are some valid arguments that can be made for pushing out features before they are complete. I’ll examine the pros and cons from my perspective later, but for now I’d like to hear from you. What do you think?
…yet.
That means I’m free to speculate about it in public. There have already been a few hints dropped here and there. Stronger 3D, parametric 3D? Does that just mean adding the missing 3rd dimension to dynamic blocks, or more? What else?
If you’re in the right spot at the right time at Autodesk University, you will probably find out a lot more. In the meantime, I’d be interested to hear your speculation about what’s going to be in 2010, and find out what you’d like to be in it. Also, what don’t you want to see?
Please add your comments, but not if it involves breaking a non-disclosure agreement. I’m hoping to hear from people who don’t know what’s in 2010, because I think that would be an interesting exercise, particularly with the benefit of hindsight in a few months’ time.
Subscription customers of plain AutoCAD 2009 can log on to the Subscription Center and download Subscription Pack 2. This pack improves PDF output (long overdue and very welcome) and adds the ability to attach PDF files. That’s welcome too, but is of largely academic interest right now because of a total lack of interoperability. Unless you only ever provide your drawing files to people who also have plain AutoCAD 2009 with Subscription Pack 2, they won’t see the PDF underlay. However, round tripping is supported, so when you get the drawing back the PDF underlay will reappear.
Here is a brief summary of the features, taken direct from the download page:
PDF Underlays
Now you can import PDF files, attaching them as PDF underlays. Once you attach a PDF underlay, you can use a variety of tools to snap to lines and objects, control the display of layers, move, scale, rotate, and clip the PDF underlay.PDF Output
Key improvements have been made for publishing PDF files. File sizes have been reduced, making it easier to share designs. TrueType font support has been added, giving you control over precisely how your fonts are displayed.This bonus pack is only available in English for AutoCAD® 2009, although, if desired, it can be installed on localized versions of AutoCAD 2009. If installed on a localized version of AutoCAD 2009, all new and related commands display in English only.
As usual, read the readme first, which contains much fuller descriptions of the new features.
Kirill Grouchnikov is a developer who has a blog called Pushing Pixels. This wouldn’t normally be of particular interest to AutoCAD users, but he recently wrote a piece describing the AutoCAD 2009 Ribbon. It is always interesting to things described from a different perspective, in this case the Ribbon from a non-user’s point of view. He pays particular attention to the ways in which the AutoCAD Ribbon differs from Microsoft’s standards. As a non-user, he has skipped lightly over several aspects of AutoCAD Ribbon use, including some drawbacks of the current implementation, but it is still a worthwhile read, as are some of the comments that follow.
Reading Ralph’s post about going back to teaching reminded me of a time some years ago when I taught some AutoCAD evening classes at a technical college. As Ralph points out, students have a wide range of abilities. Although they were all supposed to have completed a prerequisite introductory Windows course, it became apparent that during that course at least some of them must have been absent in mind if not in body.
Here’s an example, where I was explaining to the class how it was possible to modify toolbars.
Steve: “Move your mouse pointer over any toolbar button and right-click on it.”
Student: “Nothing’s happening.”
Steve: “You should see a menu appear with the word Customize on it. When it appears, left-click on that word.”
Student: “There’s no menu on my computer.”
Steve: “Did you hover over a toolbar button and right-click on it?”
Student: “Yes, and nothing happens. Do I need to press Enter?”
Steve: “No.”
Student: (Presses Enter anyway) “It says Unknown command.”
Steve: (Going over to see what’s going on) “Can you please show me what you’re doing?”
The student did so. I returned to the front of the class.
Steve: “If you haven’t already done so, hover the mouse pointer over any toolbar button, press down the right-hand mouse button and release it.”
The student had been hovering over the button and typing C-L-I-C-K. After all, I had told him to write “CLICK” on it.
Here in Australia it is well into the 21st and I raised my own glass last night, but for John McCarthy and most of my readers, it is the 20th of October right now. So this is the appropriate time to say Happy Birthday to LISP. Here’s to another 50 years of simple, compact, maintainable, efficient and elegant coding.
It is difficult to find an exact date for LISP’s birthday. It wasn’t so much born in an instant as it was gradually dragged out of the primordial slime during the heady days of late 50s computer research. What is known is that John McCarthy, LISP’s “father”, published a report in October 1958 about his new programming language aimed at providing artificial intelligence capabilities on the IBM 704 mainframe computer. That report, one of a series, was the first one to use the name LISP.
OOPSLA, a major annual conference on object-oriented programming, has decided to celebrate LISP’s 50th birthday on 20 October 2008. Practically everyone at that event is likely to be smarter, geekier and possibly even more pedantic than me. So for now I’m going to go with that date and raise a glass to LISP and John McCarthy in one week’s time.
John Walker’s almost-accidental but still inspired decision to add LISP to AutoCAD was, in my opinion, the most significant feature addition in AutoCAD’s history. There were many other feature additions without which AutoCAD would be a joke (e.g. blocks, undo/redo, dimensioning, polylines) but they were always going to happen anyway.
Adding LISP wasn’t like that. It wasn’t inevitable. It was an excellent example of Walker thinking outside the box, and it was the one thing that raised AutoCAD significantly above its competitors (yes, it had serious competitors once) at a time when the PC CAD market was still up for grabs.
The genius of this move was that instead of attempting to fill AutoCAD’s many feature holes, Autodesk could provide the tools that would let the users do that for themselves. The language was an ideal fit for a number of reasons, and users in droves started hole-filling with a vengeance. Without that boost to AutoCAD’s open architecture, the PC CAD market would have been a very different place. Autodesk itself may not even have survived into the 1990s, and I could have been writing this blog about Versacad, Computervision, or some other competitor.
Today, despite an unfortunate history of long periods of neglect from Autodesk, LISP remains the language of choice for most of my AutoCAD-related programming needs. There are exceptions, but I’ll usually first see if a given job can be done in LISP. If it can’t be done easily and well in LISP, then I will consider using one of the other available languages. For the sort of work I usually do, that doesn’t happen very often.
Why? I’ll explain my reasoning in a later post.
You may have noticed the poll on the right asking “How well cooked is the average major new AutoCAD feature these days?” Despite the rather frivolous nature of the question and choices, there is a serious side to the question so please let me know what you think.
Note that this doesn’t address the question of how well cooked new features should be, just how well cooked they are. There’s an argument that can be made in support of releasing features before they are honed to perfection, and I will be covering that issue in later posts.