Category Archives: Interoperability

DOSLib goes open source

What’s DOSLib?

DOSLib is a free library of LISP functions that adds a lot of functionality to AutoLISP/Visual LISP/BricsCAD LISP. It makes a lot of programming tasks a lot easier, because instead of writing a bunch of code to do tricky stuff, you can just load the library and call a ready-made (dos_xxx) function. There are hundreds of functions that cover the following areas (taken from the McNeel Wiki):

Drives – Check for drives, change between drives, and check available disk space.
Paths – Manipulate path specifications.
Folders – Create, rename, remove, select, and change folders. Return special operating system folders.
Files – Copy, delete, move, rename, and select files; get directory listings, search and find multiple instances of files, and change file attributes.
Print – Get and set default printers, and spool print files.
Configuration – Manipulate Windows-style initialization (INI) files, and access the Windows Registry.
Processes – Run operating system commands or other programs.
Interface – Get strings, integers, reals, and lists from the user. Display Windows message boxes, progress meters, and splash screens.
Strings – Tokenize strings, extract characters, find characters, insert, remove, and replace characters, and trim characters.
Math – Trigonometric calculations, vector manipulation, statistical analysis, and more.
CAD – Save all and close all open files. Preview drawings and list xrefs.
System – Get system information, sort lists, change the system date and time, manipulate the keyboard, and play sounds.

Why would a CAD LISP programmer use it?

There are many DOSLib functions that would be difficult to write purely in LISP and quite a few that would be impossible. So for those people who want to code for AutoCAD and BricsCAD without the bother of learning ARX/BRX and dealing with the associated compiler requirements, DOSLib has been a godsend. It’s worth noting that some of the DOSLib functions have been added to BricsCAD’s LISP engine, so depending on the function you use, you may not even need to load the DOSLib library.

Do impressive-looking stuff without writing much code. You might call it being lazy. I call it being efficient.

A history of dependability

DOSLib has been around for many years. It is currently supported on AutoCAD 2013 and later and BricsCAD Pro V13 and later, but earlier versions have supported AutoCAD releases dating back to 1992! Dale Fugier at Robert McNeel and Associates has been providing outstanding service in developing DOSLib and keeping it up to date. For nothing!

So developers have been able to take advantage of the DOSLib functionality all that time, and Dale has always come up with the goods in terms of updates to work on new releases of AutoCAD and BricsCAD. However, you may have had a nagging doubt about writing code that relies on a third party, or as a CAD Manager relying on such code, no matter how rock-solid reliable that party has proven in the past.

That nagging doubt can now be put to bed, because Dale has announced that DOSLib has been made open source under the very open and simple MIT license. The GitHub DOSLib page has the source, with compilation and other relevant information.

All good news

Dale has also stated that he intends to continue to provide compiled binaries for the foreseeable future, so don’t worry about having to mess with compilers. Even if a meteor happens to land on McNeel headquarters, it’s a pretty safe bet that somebody in the AutoCAD/BricsCAD development community will, after a suitable period of mourning, step forward to compile the code for new AutoCAD/BricsCAD releases when required.

The availability of the source code also opens the door for DWG-based applications (other than BricsCAD) to attempt to provide a higher level of LISP compatibility, to the extent of supporting (dos_xxx) function calls. That means you, the CAD LISP programmer, will have a wider potential audience for any code you write that uses DOSLib functions.

Finally, if you’re an ARX/BRX developer who wants to do something similar to something in a DOSLib function, you now have some handy sample code.

So this is all good news, and yet another example of Dale and McNeel doing the right thing by the CAD community.

Video – Steve on BricsCAD Unplugged

What’s new in AutoCAD 2019 for maintenance customers?

11 Replies

So you’re a long-term customer who has used AutoCAD since it ran on an abacus. You paid for upgrades when you could and switched to maintenance (then called Subscription) when that became the only cost-effective option for keeping current. You’re not about to fall for the subscription (rental) trick; they can prise your perpetual license from your cold, dead fingers.

It’s no secret that the value for your maintenance dollar has been poor for years. Autodesk is jacking up maintenance prices in leaps and bounds; is the maintenance being performed at a rate that matches the amount being charged?

In short, is AutoCAD 2019 enough of an advance over its predecessor to make it worth the maintenance money you paid in advance for it? This post seeks to answer that question.

What you’re not getting

As a maintenance customer, you’re being denied the big item that would make the answer to that question a definite ‘yes’ – Specialized Toolsets. Despite the name and the There Can Be Only One hype, if you’re a renter you’re not getting one AutoCAD that has the extra bits available. You’re getting the availability of a bunch of seven different AutoCAD variants and one add-on (Raster Design), each of which needs to be downloaded, installed and run individually. This initiative has been unkindly referred to as ‘shovelware’, and it’s highly likely that throwing in all of these verticals for ‘free’ means that we’ve seen the end of their meaningful lives. Expect no significant future enhancements and you may avoid disappointment. However you look at it, it’s subscription-only and therefore need not concern us further.

Similarly, as a maintenance customer you’re not getting AutoCAD Web and Mobile. Despite the names, these aren’t AutoCAD. They’re simple online viewing tools with some editing and markup functionality.

What you’re getting taken away from you

You may recall me describing (and praising) the AutoCAD 2017 feature, Share Design View. This was slightly improved in AutoCAD 2018. In AutoCAD 2019 it has been revised again and renamed to Shared Views. Presumably, the Views you’re Sharing are no longer of Designs. Whatever the reason for the rename, it has a sinister connotation. Share Design View is considered obsolete and has been removed. Shared Views has been provided only to subscription customers. The upshot is that this is a feature removal. Yes, you’re getting negative value for your maintenance dollars. This is one of the more petty, vindictive attempts to convince you to go rental. Whoever put their hand up at the product meeting to suggest this particular piece of anti-customer nastiness probably got a gold star from Andrew Anagnost, but I don’t approve and I think it is likely to prove counterproductive.

Another feature that has been removed from AutoCAD in 2019 is the ability to export to FBX files. If you didn’t use this feature, you won’t care. If you used it as the basis of a Virtual Reality workflow to allow you to get your DWG 3D models into, say, Unity to create a virtual environment, then you will probably care a great deal. Similarly, FBX import has also gone. Autodesk’s suggestion that you use the DWG import and export feature in their other products instead is no use at all to you if you don’t use those products in your workflow.

Because Autodesk A360 has been deprecated, a bunch of related commands have also gone AWOL. The lesson here is to not get too used to any Autodesk cloud-based workflows; they could vanish on a whim at any moment.

What you’re getting

What’s left? What are you getting for your hard-earned? Here are some enhancements:

Some of the icons have been slightly modified. This includes the status bar icons. Unfortunately, Autodesk remains deaf to the many requests for the return of text to this area.
2D graphics performance is supposedly improved.
The Graphics Performance dialog box now has a 2D section.

OK, these are minor tweaks. Some are welcome (performance), others (icon tampering) are just tinkering that nobody will care about. How about worthwhile new functionality?

Well, there’s one feature that many will find useful: Drawing Compare. But wait! Isn’t that new? Well, no. Let’s put aside the fact that this is just playing catch-up to a core BricsCAD feature. Purely within the AutoCAD world, it’s still not new. Drawing Compare has been available as an Autodesk-supplied free app since 26 April 2012. It’s still available now for AutoCAD 2016 and later, even though the one for 2013 to 2015 has been ‘unpublished’.

I’ll examine the differences between the AutoCAD 2019 core feature, the AutoCAD add-on and the BricsCAD core feature in a future post. I can tell you that Edwin Prakaso thinks the old add-in is better than the core feature, but I’ll compare the compares for myself and you can make up your own mind.

Summary

For Autodesk giveth (a bit) and taketh away (a bit more). Overall, maintenance customers are down on the deal. Customers are paying ever-increasing amounts for tiny or even negative benefits. Why do they bother?

Importing SketchUp files into AutoCAD

2 Replies

Do you have a SketchUp (SKP) file you need to import into a DWG? Need to know how to do it? Tried it but it didn’t work? This tip is for you.

If you’re using AutoCAD 2016 to 2019 for Windows, you can download and install the SketchUp Import plug-in from the Autodesk App Store. If that goes according to plan, this will add the command IMPORTSKP to AutoCAD. You may need to restart your AutoCAD first. It’s straightforward enough; select a file to import and it becomes a block in your drawing.

Reading the reviews for this add-on, it’s clear that it’s not working for many people. If it does work, it only imports SketchUp files up to 2017 format (2016 on 32-bit AutoCAD).

What if it doesn’t work? What if it does work but you have an unsupported 2018 version SKP file? Well, this post could arguably fit into the Why every AutoCAD CAD Manager should have a copy of BricsCAD series, because this is an example of BricsCAD acting as a workaround for AutoCAD limitations. SketchUp files are supported in BricsCAD’s native Import command, no add-ins required. If you have BricsCAD V18.2.10 or later, 2018 version SKP files are supported. If you have an earlier version of BricsCAD you can download the latest here.

Importing SKP files is also supported in the free BricsCAD Shape application, but at the time of writing the version is V18.2.06, which only supports SKP files up to 2017 format.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 6, future proofing

2 Replies

This is the sixth and final post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post explains why adding a copy of BricsCAD to your stable of AutoCAD licenses is a good thing for your future and that of your company.

A CAD Management thing I did a few years ago was to examine the options for replacing AutoCAD and other Autodesk products. I was an AutoCAD loyalist (albeit a somewhat critical one) with over a quarter of a century invested in it. I was looking after the deeply entrenched and very heavily customised CAD environment of a major public utility company that had been using AutoCAD as its primary CAD system since the late 1980s. Hundreds of custom commands were in place and providing priceless productivity benefits. Hundreds of thousands of DWG files were on file, with thousands more coming through every month. The inertia behind AutoCAD was very, very strong. Looking outside the cage was a pretty radical step to take. What led me to that point?

Autodesk business policy. Autodesk has become increasingly anti-customer over the years in ways that will be familiar to all readers of this blog. I won’t rehash them here. This leads to…
Increasing costs. Autodesk software is expensive and getting more so. Autodesk has made no secret of its intention to move to an all-subscription (rental) model. This is an attempt to treble the ongoing income Autodesk receives, in return for doing as little as possible. Which leads to…
Lack of progress. It had become clear that the days of AutoCAD seriously improving from release to release were over, never to return. This isn’t because there is no room for improvement, it’s because Autodesk doesn’t want to improve AutoCAD. AutoCAD won’t be permitted to become too capable because that would just eat into sales of Autodesk’s other products. You’re not going to see 3D parametrics or sheet metal capabilities in AutoCAD: buy Inventor instead. You’re not going to see BIM capability: buy Revit. Beyond the internal competition issue, some years ago, Autodesk leadership lost interest in what it perceived to be an old-fashioned dead-end product. The income from AutoCAD customers is being diverted to fund purchase and/or development of more fashionable and interesting products.
Frustration with Autodesk’s Beta program. The goings-on within the Autodesk Beta program must remain private, so what I can say here is limited. I can say that I spent many years contributing large numbers of hours to that program in order to attempt to improve the product. As time went on, the positive results that emerged from that effort decreased; that much is no secret because it is apparent in the product. I felt I was fighting against Autodesk to try to improve the product, and losing. There were a few final incidents that persuaded me to stop bashing my head against that particular wall. I wasn’t the only one. I stuck it out for years longer than many very valuable people who had already given up before me.
Proxy server issues. Over the years, Autodesk’s habit of attempting to do sneaky things to access the Internet had caused a variety of problems in a secure proxy server environment. This caused several things not to work, and harmed performance severely in some places. As Autodesk’s developers turned over, things that worked in one release would not work in the next. Attempts to get this addressed as a support issue would result in the environment being blamed. These problems increased over the years as Autodesk threw in more and more connectivity-requiring features. There was a non-zero and ever-increasing possibility that one day, Autodesk would screw things up altogether and leave us with non-functioning software. That has already happened for some people, and although the stoppage has generally been temporary, it is important to have redundancy.
Poor performance. AutoCAD has been getting bigger and slower. Downloads are huge and Autodesk does its best to make them as difficult as possible. Installations take an age, as do uninstallations. Startup times are terrible and getting worse. My users were complaining – a lot – and there wasn’t much I could do about it.

That’s what moved me to take a very, very serious look at alternatives. Your motives may differ. Just the desire to have a Plan B in case of disaster might be enough.

If you don’t feel moved to investigate, you may eventually be faced with no option. Sooner or later, the person who holds the purse strings at your company may point to this year’s much bigger Autodesk invoice and ask, “What are we getting for this? How can we reduce our costs?” When that happens, you don’t want to be scrabbling round for answers before that invoice needs to be paid. Look into the options in advance. Are you really wedded to AutoCAD or are you actually tied to DWG?

Days of Future Past

Here’s my suggestion. Examine the available alternatives to AutoCAD and the other Autodesk products you use. Do it sooner rather than later so you get the chance to determine the answers to non-trivial questions like these:

Capability. Does the alternative product do everything that AutoCAD does, that your users need it to do? Does it do other stuff that AutoCAD doesn’t that you might find useful? What’s the performance like? How does it work on the hardware you have? Does it have user interface elements that don’t just look good but work productively in practice?
Compatibility. You will almost certainly demand extremely good DWG compatibility, but this question goes well beyond that. Will your LISP work? How about DCL? ActiveX support? DOSLib? Other programming languages? Can you carry over your customisation files? Can you make the interface look the same? If you have custom toolbars, or ribbon, or even image menus, do they carry across? Can your users carry across their skills without downtime, extensive training and a productivity hit? Can AutoCAD and the potential replacement coexist without issues? Can you use a common set of custom support files pointed at by both products? Will it work well on your hardware?
Add-ons. If you’re using third party products on top of AutoCAD, or if you’re using an AutoCAD-based vertical, is that product or an equivalent available? Does it work well? What do the objects they create look like in plain AutoCAD? Can you round-trip through AutoCAD and back and retain your intelligence? You’re probably going to have to test this with evaluation software and your own data.
Licensing options. Is perpetual licensing available? Can you stick on a release for a few years and still purchase upgrades later? Has the company committed to providing you with licensing options or has it made noises about going all-rental? Is network licensing available? Does it coexist problem-free with Autodesk’s network licensing software?
Costs. Compare the likely costs for all your options over several years. You’re going to have to make some assumptions. It can be difficult to work out what they should be.
Track record. Has the company been around for a while? What reputation does it have? Does it treat its customers with respect? How good is the support?
Future prospects. Is the company likely to be around long-term? Is it actively developing the product you’re interested in? Is it innovating? Is it merely following AutoCAD at a distance or charging ahead? Is the product going to be limited by Autodesk-like internal competition?

I went through all of these questions and settled on BricsCAD as the best option in my company’s case. In fact, several aspects made it really the only viable option. The product impressed me with high performance, capabilities well beyond AutoCAD in several important areas, a very high degree of compatibility (particularly LISP but also other customisation files), the availability of perpetual licensing and much lower ongoing costs. The company impressed me with its honesty and attitude toward customers.

Most of all, I was won over because I could see that the product had a future. Subsequent improvements have only strengthened that view.

Obviously, you need to make your own judgement based on your own circumstances. I would suggest looking at all the options, including sticking with AutoCAD permanently, with or without subscription or maintenance. Maybe you can use my investigations as a starting point, but I encourage you to start investigating now rather than when you’re under time pressure and don’t have time to do a thorough job.

It will cost you a few minutes to download and install of an evaluation BricsCAD and start preparing for the possibility of a different future. Maybe it won’t turn out to be part of your company’s future, but it could still be part of your future.

Options are good. Learning is good. Best case scenario, your knowledge is going to save your company money and improve its productivity, and you will end up smelling of roses. Worst case scenario, you’re going to spend some very justifiable time doing something new, different and interesting. I recommend it.

Other posts in the Why every AutoCAD CAD Manager should have a copy of BricsCAD series:

Part 1, fixing drawings
Part 2, 3D operations
Part 3, parts on demand
Part 4, efficiency
Part 5, LISP

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 5, LISP

5 Replies

This is the fifth post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about BricsCAD being better than AutoCAD at the one thing that made AutoCAD win the race against its competitors back in the 80s – LISP. That is, AutoLISP (added fully to AutoCAD in Version 2.18) and Visual LISP (fully integrated with AutoCAD 2000).

If you’re a good AutoCAD CAD Manager, you’ll already know the reasons LISP is an extremely important tool, so I won’t cover them here. I may explain those reasons in a later post, but that would distract us from the main point. Why is having a copy of BricsCAD useful to a CAD Manager?

BLADE. I’ve covered the BricsCAD LISP Advanced Development Environment in various posts already, and I intend to go into greater detail in future posts. There are enough advantages over VLIDE to warrant an entire series of posts. This is simply the biggest advance for CAD LISP in 20 years; if you’re doing any reasonably complex development in LISP and you’re not BLADE, you’re wasting time and money.
Performance. Because BricsCAD’s LISP engine is much more modern than AutoCAD’s, the performance is much greater. In my experience, it’s about three times as fast. Some function calls are as much as 30 times as fast. If you have a user who’s complaining that your routine is taking an age to process in AutoCAD, try it in BricsCAD instead. I once saved a user half an hour in processing time for one polyline by using BricsCAD. Another aspect that will benefit you when programming and testing is BricsCAD’s generally superior performance. Got nothing running and want to get programming in the next 5 seconds? Fire up BricsCAD. Want to do a complex process on a big drawing that makes AutoCAD run out of RAM? Try it in BricsCAD.
Licensing. While you’re developing in BricsCAD, you’re not using up an expensive AutoCAD license. You’re using a cheaper (or even free, while you’re evaluating it) BricsCAD license. Also, it’s a perpetual license so if you ever stop paying, you can keep developing as long as you like. Oh, and it’s not going to flake out on you on those days where Autodesk’s subscription licensing server has a meltdown.
Extra functionality. BricsCAD’s LISP has the AutoLISP and Visual LISP functions and then some. Some of the DOSLib functions are available without even needing DOSLib, but if you need the full set of DOSLib functions they can be loaded, as per AutoCAD. A range of extended functions are available with the vle- prefix, and the LISP Developer Support Package documents these and provides the source code so you can also use them in AutoCAD.
Platform independence. AutoCAD for Mac has severely restricted LISP capabilities, making it unsuitable for use in a professional, efficient custom environment. BricsCAD for Mac and BricsCAD for Linux both provide practically identical functionality to the Windows version. Yes, BricsCAD for Mac really is significantly more AutoCAD-compatible than AutoCAD for Mac.

I do my LISP development in BricsCAD these days, and can attest that it’s well worth the investment in time to get the hang of BLADE.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the LISP situation for yourself.

Edit: it’s not just LISP. See James Maeding’s comment below about .NET, too.

Steve’s BLADE presentation at the BricsCAD New Zealand and Australia Roadshow

3 Replies

Sofoco (Australia) and CAD Concepts (New Zealand) recently ran a series of seminars throughout Australasia demonstrating BricsCAD. I attended the last of these in Brisbane on April 19 and gave a presentation about BricsCAD’s LISP, with reference to AutoCAD compatibility and the tools available to CAD Managers and developers, including BLADE. The talk was aimed at anybody who is writing or maintaining LISP code for AutoCAD or BricsCAD.

I had the just-before-lunch slot, which is never desirable for a presenter. People are dozing off and/or bursting to go to the toilet, and time adjustments have to be made if earlier presentations run over. I started 10 minutes late and therefore had to remove the demonstration part of the presentation on the fly, but I had planned to allow for that eventuality. It’s been a while since I have presented like this before an audience so I was a bit rusty and it wasn’t as free-flowing as I would have liked. Too many ‘erms’!

Steve’s invisible accordion is impressively large

I did manage to keep the whole audience in their seats until the end, though, so that’s something. Maybe the fact that I was waving a sword around had something to do with it.

Here’s my video, which is 21 minutes long. The sound is a bit muffled and my accent is Australian, so you might want to turn on subtitles using the CC option in the YouTube player.

Disclosure: the organisers covered part of my expenses.

Steve at the BricsCAD New Zealand and Australia Roadshow

Why One AutoCAD is smart strategy

4 Replies

OK, so Autodesk may have blown the AutoCAD 2019 rollout, triggering an apology from CEO Andrew Anagnost.

OK, AutoCAD 2019 may have the smallest set of significant advances in the history of AutoCAD releases. If you’re wondering, I give it 1/10. The “there can be only one” hype could easily refer to meaningful improvements to the product per year. This year’s improvement is… drawing compare!

Still, AutoCAD 2019 is a significant release for reasons beyond the content of the core product. An examination of the One AutoCAD strategy reveals a collective corporate mind that’s smarter than it’s being given credit for.

In case you’ve missed it, the idea behind One AutoCAD is that if you subscribe to AutoCAD, you can now also get a bunch of vertical variants of AutoCAD thrown in, renamed as “Toolsets”. You need to ask for it, and it’s for renters only, no perpetual license owners need apply. Oh, and Civil 3D isn’t part of the deal.

This concept has been received less than enthusiastically among respected independent observers such as Ralph Grabowski and Robert Green. I’m going to go against the trend a little and point out several ways in which this is a smart move for Autodesk.

It represents the first time Autodesk has had anything of substance to positively differentiate between maintenance and subscription. Until now, it’s all been negative: give away your perpetual licenses to avoid forthcoming maintenance price increases.
It provides some substance to Dr Anagnost’s “give us a year to show the value of subscription” request to customers. OK, it may have taken a lot more than a year, but at least it’s now possible to point to something that customers can gain by subscribing, rather than having the embarrassment of an empty promise hanging around.
It acts as an effective distraction from yet another price rise (7% on top of Autodesk’s already sky-high subscription costs). Yes, this new price still applies even if you don’t use the toolsets. Yes, it still applies even if you’re a Mac user who doesn’t have these toolsets available.
It will almost certainly be used as justification for future subscription price rises. How can you complain about a few more dollars when you get all those products included in the price?
This stuff has already been developed to a point that Autodesk considers mature (web apps excluded), and it isn’t costing Autodesk anything to “give it away”.
It means that the glacial or non-existent rate of improvement of AutoCAD and its variants suddenly appears less important. How can you complain that nothing worthwhile has been added to your AutoCAD variant this year when you now have access to hundreds more commands than you used to have? This line has already been tried with me on Twitter.
It provides a marketing counter-argument against competitors who sell DWG-based AutoCAD-compatible products that provide above-AutoCAD standards of functionality (e.g. BricsCAD).
If an increased number of users start using the vertical variants, there will be increased pressure on those competitors to handle the custom objects created using those variants. This will act as a distraction and reduce the ability of those competitors to out-develop Autodesk at the rate that has been occurring for the past few years.

There are a couple of flies in Autodesk’s One AutoCAD ointment:

Critical mass – it has yet to be seen how many customers are so won over by this concept that they sign up for it. Remember that it’s only available to a minority of customers anyway, and if the bulk of customers remain reluctant to give up their perpetual licenses then all this is moot. If the move-to-rental numbers are small, then the anti-competitive nature of this move is negated. The marketing gains still apply, though.
Interoperability – traditionally, the AutoCAD-based verticals add custom objects to the core AutoCAD objects, which when opened in vanilla AutoCAD or another vertical, appear as proxy objects that either don’t appear or will provide very limited access. Improved but still limited access can be provided if Object Enablers are installed. Object Enablers are not always available for the AutoCAD variant you want to use. LT? Mac? Old releases? Forget it.This has always been a highly unsatisfactory arrangement. I have worked for a company that explicitly prohibits drawings containing proxy objects and rejects any it receives, and that has proven to be a smart policy. Also, the vertical variants of AutoCAD have always had hidden DWG incompatibilities built in. AutoCAD 2015 user? Try to use a DWG file that has been created in a 2017 vertical variant. Good luck with that, even though all those releases supposedly use 2013 format DWG. Paradoxically, you can expect to experience much better DWG interoperability with non-Autodesk products and their add-ons than you will with AutoCAD and its verticals, because the non-Autodesk products are forced to work with AutoCAD native objects. It remains to be seen how, when, or even if Autodesk addresses these issues.

In summary, this strategy has potential to significantly benefit Autodesk. Will it work? That will largely depend on how many customers are prepared to put aside their mistrust enough to hand over their perpetual licenses to Autodesk. That mistrust is mighty large (Autodesk’s been working hard for years on building it up) and recent sorry-we-broke-your-rental-software events have reiterated just how valuable those perpetual licenses are.

Autodesk has produced what it considers to be a very attractive carrot. Is it big and juicy enough to attract you?

How to get your Wacom Graphire 4 tablet working in Windows 10

67 Replies

I’ve been setting up a new PC at home and one of the things I struggled with was getting my Wacom Graphire 4 tablet working. This isn’t a CAD tablet (remember those?); instead, I use its pressure-sensitive stylus for image creation and editing. Press harder and you get more ink. Turn the pen over and you automatically erase instead of drawing. Press the eraser harder and you get more erasing.

I use PaintShop Pro for my image work, by the way, not Photoshop. You can still buy and optionally upgrade PaintShop Pro perpetual licenses, which is how it should be. You’re probably aware that I don’t rent stuff unless there’s no realistic alternative.

According to the Wacom FAQ, I was severely out of luck.

What is the latest driver for the Graphire 3 & 4 (CTE) tablets?
The Graphire 3 & 4 CTE tablets made from 2003-2007 are no longer supported by Wacom and will not work with a current tablet driver. Below are links to the latest drivers available for these tablets.

Windows 8, Windows 7, Vista & XP Download Here
Mac 10.8, 10.7 & 10.6 Download Here

Not one to give up so easily, I tried a variety of drivers for my tablet (model CTE-440). They were either blocked from installation by Windows 10×64, or in the best case scenario failed to provide any functionality other than acting as a basic mouse. The tablet failed to appear as a WinTab device, so I couldn’t configure PaintShop Pro to use its pressure-sensitivity, defeating the object of having the thing in the first place.

So I did what I thought was best and put the tablet out on the verge with the other junk awaiting council collection and investigated a replacement. Not from Wacom, obviously! I don’t want to reward a company for abandoning its products. I was checking out Huion tablets, which are so much cheaper than Wacom’s that it’s probably worth taking a punt and buying one anyway.

But then the stubborn streak in me (have you noticed?) kicked back in and I had one last go. A bit more in-depth Googling led me to this page. This is an old, non-maintained, leftover page from Wacom Europe. Let’s hope it stays there. On that page I found the driver I needed: DRIVER 5.30-3 RC FOR WINDOWS 8, WINDOWS 7, VISTA, AND XP. The direct link to the driver installation executable (cons530-3_int.exe) is:

http://downloadeu.wacom.com/pub/WINDOWS/cons530-3_int.exe

I retrieved my tablet from the junk pile, installed that driver, cleaned off my tablet while my system rebooted, plugged it in and away I went! In PaintShop Pro 2018, the setting is found at File > Preferences > General Program Preferences in the Miscellaneous section.

Wacom’s FAQ gave me a bum steer. Yes, the driver I used isn’t supported in Windows 10 and it isn’t current, but I don’t care. It works just fine and means my perfectly good as-new tablet isn’t landfill. Wacom needs to do better both in terms of supporting its hardware with current drivers and providing more useful information to its customers.

Setting your application or document window size using LISP

1 Reply

I intend to produce a few videos containing tips, tutorials, product comparisons and the like. I’ve set up a cad nauseam YouTube channel, but don’t bother visiting it yet because it’s empty.

One of the things I need to do for these videos make sure I’m capturing the screen at an appropriate resolution. I knocked up a bit of Visual LISP to take care of this task quickly and accurately, and you might as well have it. It’s a simple routine that allows you to accurately size either the main AutoCAD application window or the current document window (drawing area) within the main window.

The file is WindowSize.lsp. It should work in all full AutoCAD releases (not counting LT and AutoCAD for Mac) and AutoCAD-based verticals from 2000 on.

It works in recent BricsCAD releases (except the free and LISPless BricsCAD Shape). I’ve only tested it in Windows, but it should also work in the Mac and Linux versions due to the high degree of LISP compatibility provided even across platforms. It also works in ZWCAD 2018 for the main application window, but don’t use it on the document window because that doesn’t work.

Download it, put it in a location of your choice and load it into your CAD application (for example by dragging and dropping it from Explorer onto the drawing window).

Note: In AutoCAD 2014 and later, loading any LISP or other executable file may result in a warning depending on the release, the security settings, whether the file is located in one of AutoCAD’s trusted locations, and whether the file is digitally signed. I’ve digitally signed the file to reduce the incidence of warnings, but you could still see something like this:

The verified publisher should be cad nauseam as shown above. If you pick Always Load then you shouldn’t see the warning again for this file or any others signed by cad nauseam. Feel free to edit the file for your own needs, but if you do the signature will become invalid and you’ll be warned again when loading the file.

Once it’s loaded, enter the command WindowSize. The prompt sequence goes like this:

Command: WINDOWSIZE Window to size [Application/Document] : Width in pixels <1280>: Height in pixels <720>:

Now, back to work on the first of those videos.

AutoCAD 2018 – 2/10, would not rent

26 Replies

It must be March, because another AutoCAD has just been launched. Despite this one being codenamed Omega, I’ve been assured it’s not the final AutoCAD release. The good news is that AutoCAD 2018 is twice the upgrade that 2017 was. But hold your excitement, because the bad news is that 2017 was only a 1/10 upgrade.

Autodesk has continued the well-established tradition of acting like a low-quality sausage machine, reliably popping out consistently unexciting products at regular intervals.

Here’s what’s in this year’s underwhelming sausage:

Xrefs now default to relative path attachment and there are a few associated tweaks including find/replace path
You can select objects off-screen (handier than it sounds)
File dialogs remember settings
A couple more dialogs can be resized
There are a couple more tiny user interface tweaks
The stuff from 2017.1 is included, of course, some seeing minor improvements since then
iDrop support is gone (will anybody miss this?)

Thrilled? Me neither. The xref stuff is worthwhile, and Autodesk does deserve credit for not adding any seriously undercooked “headline” features or pointless eye candy. That, along with the 2017.1 stuff, quietly fixing some old bugs, sorting out a few old feature issues and some unsung but worthy API documentation improvements, is just about enough to make this a 3/10 upgrade.

But wait! Autodesk earned itself a minus point to take it from 3 to 2 by inconveniencing customers with yet another API change (so your 3rd party stuff will need updating), and most unfortunate of all, a DWG format change. We had grown used to enjoying a lack of compatibility issues (with plain AutoCAD, anyway – don’t get me started on the verticals), thanks to the 2013 format surviving five releases rather than the traditional three. Now that’s over.

Why does AutoCAD 2018 need a new DWG format? It probably doesn’t. The 2013 DWG format is capable of holding pretty much anything you want, as Bricsys has shown with BricsCAD V17’s ability to compatibly store 3D parametrics and (optional) BIM and sheet metal features within that format. The changes to AutoCAD 2018 don’t come anywhere near that level of complexity. Although Autodesk cites performance reasons with certain drawings, I strongly suspect the new DWG format was introduced purely to make life difficult for competitors, and to encourage wavering customers to stay with Autodesk for fear of losing compatibility. In other words, it seems likely this is an anti-competitive change rather than a technical one.

Oh, and the desktop icon is the same as 2017, so if you run both releases side by side while you’re waiting for your add-ons to be updated, you’ll find it difficult to see at a glance which shortcut is which and what’s already running. Minor irritant, but an unnecessary cheapskate move.

There are alleged to be performance improvements; probably true in places. I did notice a slight improvement in 3D Orbit performance, with AutoCAD 2018 now about up to BricsCAD standards. However, this aspect of AutoCAD 2017 performance wasn’t a problem with the sub-20 MB drawings anyway, so you may not notice a difference.

In my experience with the Beta, AutoCAD 2018 was frequently appallingly slow, particularly start-up time, which was atrocious. Those 14 million lines of code have added up over the years, and AutoCAD 2018 is bloatware; literally ten times the size of the more fully-featured BricsCAD V17 Platinum, which starts up in the blink of an eye. However, I will reserve final judgement on AutoCAD 2018 performance until I have had chance to properly test the production version. I have not factored performance in to my overall mark.

There’s nothing in this release that comes close to justifying the annual maintenance fees, let alone throwing away your perpetual license and signing up for subscription. If Autodesk wants customers to think it will be worthwhile signing up for a lifetime of rental fees in the hope that substantial improvements will result, this weak release represents a singularly unconvincing argument.

Overall, 2/10. This is a sub-mediocre release that shows once again that AutoCAD is in maintenance mode. Autodesk appears completely disinterested in AutoCAD other than as a cash cow, and severely lacking in imagination about ways of seriously improving it. Omega might not be the final AutoCAD release, but given the glacial level of improvement being shown, it might as well be.

BricsCAD’s LISP kicks sand in the face of AutoCAD’s

10 Replies

If you’re a power user or CAD Manager transitioning from AutoCAD to BricsCAD, one of the things you’ll like is that almost all of your LISP routines will just work. That’s not an statement that can be made about various Autodesk products that bear the AutoCAD name, such as AutoCAD 360, AutoCAD LT and AutoCAD for Mac.

It’s not just simple old AutoLISP code that runs in BricsCAD, but complex dialog routines that use DCL, and Visual LISP stuff that uses ActiveX. Yes, even on the Mac and Linux platforms. Some DOSLib functions are built in and the rest can be loaded, as with AutoCAD. Even OpenDCL is supported. It’s a quite astonishingly high level of compatibility.

But it’s not 100%. There are minor incompatibilities, system variable and command-line differences that cause problems in a handful of cases. It’s often possible to work around these and still retain the same code that works in both AutoCAD and BricsCAD. Reporting LISP bugs and incompatibilities to Bricsys generally gets them fixed super-quick.

Also super-quick is the speed at which your code will run. It’s immediately noticeable when running any LISP code that needs to do a bit of processing that it just gets done faster in BricsCAD than AutoCAD. Fast enough to extract the following comment from one of my AutoCAD users trying out a linework cleanup routine in BricsCAD:

Wow.

User impressions are one thing, but how about measurements? Today, I had a support job to do that involved running one of my LISP routines. I ran it on both AutoCAD 2017 and BricsCAD V17 on the same PC. AutoCAD took 2970 seconds (about 49 minutes), BricsCAD 1030 seconds (about 17 minutes). Over half an hour saved on one operation. That’s 2.88 times faster, which is consistent with my previous observations with a variety of routines.

Upshot: if you’re doing work where there’s a lot of LISP processing going on, switching to BricsCAD is going to save you a shedload of time.

There is a downside to BricsCAD’s LISP, and it’s a big one; no VLIDE. No equivalent, either. There are various programming editors around that can help with editing code, but no substitute for integrated debugging. It means if you’re a power user, CAD Manager, developer or support person, you’re probably going to have to keep one working copy of AutoCAD around even after you’ve completed the transition to BricsCAD.

Because VLIDE has been in maintenance mode for over 15 years it remains virtually unchanged year after year (including ancient bugs). So it doesn’t matter that much which AutoCAD release you have hanging around. Assuming you’re a perpetual license holder, when you drop the maintenance contract on one of your AutoCAD licenses, you’re entitled to keep using the software as long as you wish, albeit only the current release at the time the contract ends. How long the software will keep working is another matter, depending as it does on factors not entirely within your control.

This is an imperfect solution. Even keeping a copy of AutoCAD around won’t help much if you’re debugging a problem caused by something specific to BricsCAD. Filling the VLIDE hole is something Bricsys needs to work on.

AutoCAD 2017 for Mac released, still half-baked

4 Replies

AutoCAD 2017 for Mac and AutoCAD LT 2017 for Mac have been released. Here’s a video highlighting exciting and innovative new features such as drawing and layout tabs. Despite such stellar advances, it’s safe to say that AutoCAD for Mac remains half-baked, even after all these years. Don’t say I didn’t warn you.

According to Autodesk, these are the features missing from AutoCAD 2017 for Mac:

LAYDEL, LAYMRG, LAYWALK and LAYVPI
Tool palettes
New layer notification
Navigation bar
ShowMotion
Ribbon*
DesignCenter**
Sheet Set Manager***
Steering wheel
Feature finder for help
Model documentation tools
Dynamic block lookup parameter creation/editing
Table style editing
Multiline style creation
Digitizer integration
Geographic location
Simplified, powerful rendering
Material creation, editing, and mapping
Advanced rendering settings
Camera creation
Point cloud
Walkthroughs, flybys, and animations
DWF underlays
DGN underlays
Hyperlinks
Data extraction
Markup set manager
dbConnect manager
WMF import and export
FBX import and export
Design feed
Import SketchUp files (SKP)
Design share
3D print studio
Reference Navisworks models
Right-click menus, keyboard shortcuts, and double-click customization
VisualLISP
.NET
VBA
DCL dialogs
Action recorder and action macros
Reference manager (stand-alone application)
Password-protected drawings
Digital signatures
Workspaces
User profiles
Autodesk desktop app
Migration tool enhancements
CAD standards tools
CUI import and export
BIM 360 add-in
Performance Reporting
Sysvar monitor

* To be fair, AutoCAD 2017 for Mac does have a Ribbonesque feature, albeit one that that looks more like the pre-2009 Dashboard than the Windows-style Ribbon.

** Autodesk claims Content Palette to be roughly equivalent to DesignCenter, but it claimed that (wrongly) about the awful and short-lived Content Explorer. It’s wrong here too; Content Palette on Mac has nowhere near the functionality of DesignCenter on Windows.

*** Autodesk claims AutoCAD for Mac’s Project Manager is functionally equivalent to the missing Sheet Set Manager.

Also, some PDF export features don’t work when plotting, only when using Publish.

No workspaces? No model documentation? No hyperlinks? No table style editing? Various kinds of reference files unsupported? No Visual LISP or DCL? Still? Come on Autodesk, you’re not even trying.

That’s before we get on to the lack of third party applications, vertical variants and object enablers. Is Autodesk expecting full price for this thing? Really?

It’s not all bad news, though. Not having Autodesk desktop app is no handicap at all. Also, according to Autodesk the following features are unique to AutoCAD for Mac:

Coverflow navigation
Multitouch gestures
External reference path mapping
OpenGL Core Profile support
OS notification for updates
Language switching in product

Well that’s all right, then.

Any BricsCAD users out there? v.2016

8 Replies

Back in 2010 I asked the question Any BricsCAD users out there? and there were a few of you who had tried to replace AutoCAD with BricsCAD. Most who responded had made the change successfully, others not so much.

Six years on, the situation is different. The fact that you can’t buy a permanent AutoCAD license any more has prompted some Autodesk customers to look more seriously at alternative vendors who do provide that option. Bricsys is one of those vendors, and their DWG-based AutoCAD alternative BricsCAD has improved way more rapidly than AutoCAD over the same time period. No, that isn’t a guess, I’ve been keeping an active eye on things. BricsCAD today is by no means perfect, but it’s impressive in many ways. LISP compatibility and performance are excellent, for example. BricsCAD v16 superior to the also imperfect AutoCAD 2017 in several areas, despite the total cost of ownership being significantly lower.

Here’s the question I asked back then:

I would be very interested to hear from any of you who have adopted BricsCAD (either partially or fully replacing AutoCAD or AutoCAD LT in your organisation), or at least seriously investigated using the product.

Why did you investigate changing over? How far have you gone? What are your experiences? What are the pros and cons? How is performance? Reliability? Bugs? Ease of use? Familiarity? Support and other aspects of customer service? Total cost of ownership? Are you experiencing interoperability problems when exchanging drawings with Autodesk software users? How did you go with incorporating in-house customisation and third party tools?

How would you answer that question today? Would you be interested in me providing more posts about BriscCAD, such as practical experiences with attempting a transition from AutoCAD?

AutoCAD 2013 for Mac – the holes live on

20 Replies

A couple of years ago, I reported on the missing features in AutoCAD 2011 for Mac. While some generous souls were prepared to accept something half-baked as a first attempt, even that excuse doesn’t wash when it comes to a third iteration. So how well is Autodesk doing at filling those holes? Decide for yourself. Here’s an updated list of missing features in AutoCAD 2013 for Mac:

Quick Properties Palette
Layer State Manager
New Layer Notification
Various layer commands including LAYCUR, LAYDEL, LAYMRG, LAYWALK, and LAYVPI
Autocomplete doesn’t work entirely properly, including offering commands that don’t exist
Filter
Quick Select
DesignCenter
Tool Palettes
Navigation Bar
ShowMotion
Sheet Set Manager (but there is Project Manager)
Model Documentation Tools (but at least now there are object enablers)
Geographic Location
Table Style Editing
Hatch Creation Preview
Multiline Style Creation
Digitizer Integration
Change Space
Express Tools
Material Creation, Editing, and Mapping
Advanced Rendering Settings
Camera Creation
Walkthroughs, Flybys, and Animations
Point Cloud Support
DWF Underlays
DGN Underlays
Autodesk 360 Connectivity
Data Links
Data Extraction
Hyperlinks
Markup Set Manager
dbConnect Manager
eTransmit
WMF Import and Export
FBX Import and Export
Additional Model Import
Ribbon Customization
Right-click Menus, Keyboard Shortcuts, and Double-Click Customization
VisualLISP
.NET
VBA
DCL Dialogs
Action Recorder and Action Macros
Reference Manager (Standalone Application)
Dynamic Block Authoring
Custom Dictionaries
Password-protected Drawings
Digital Signatures
Workspaces
User Profiles
Migration Tools
CAD Standards Tools
CUI Import and Export

Many of these are big-ticket, dealbreaking items. No DCL? Still? Seriously? To these we can add a whole application, Inventor Fusion, which comes as part of the AutoCAD 2013 for Windows install set. (Edit: Inventor Fusion for Mac is available to download as a Technology Preview application from Autodesk Labs and from the Apple App Store). I don’t expect many Mac users will be heartbroken about the lack of a permanent Ribbon (although there are Ribbon-like things that come and go), but as Autodesk reckons it’s responsible for a 44% productivity boost, maybe they should be. Oh, and it isn’t supported and doesn’t work properly on the current release of OS X.

To be fair, it’s not all one-way traffic. Here’s the list of features that appear only in AutoCAD for Mac:

Content Palette
Coverflow Navigation
Multi-touch Gestures
Project Manager (instead of Sheet Set Manager)

Well, that’s all right, then.

We’re used to Autodesk’s unfortunate mastery of the long-term half-baked feature, but carrying on with a whole product this unfinished for three releases is more than a little embarrassing. Charging the same amount for it as real AutoCAD adds insult to injury. While I’m sure there are dozens of Mac users happy to be using anything with the AutoCAD name on it on the platform of their choice, this is not a sustainable state of affairs.

Autodesk really needs to make up its mind about this product before embarking on more Mac misadventures such as porting Revit and other products. Autodesk needs to either take AutoCAD for Mac seriously and finish it off to an acceptable standard, or kill it off as a bad idea. As there’s no sign of the former happening and Autodesk history is replete with examples of the latter, I wouldn’t suggest anybody gets too attached to running AutoCAD natively on OS X.

Source: Autodesk knowledgebase article TS15833488.

Cloud concerns – tie-in

4 Replies

One of the major attractions of the Cloud for vendors is that it ties in customers, providing a reasonably consistent revenue stream. It is an effective anti-competitive strategy. There are various technical and other methods that can be used to ensure that it’s difficult or even impossible for customers to jump ship. While that’s all very nice for vendors, it’s not such a wonderful thing for customers.

Let’s say you’re a CAD Manager who persuades your company to use a great new SaaS service and Cloud storage. Let’s assume it performs well, is secure, has 100% uptime and offers functionality that is not available with standalone software. Your company is pleased with all this and uses it increasingly over several years, eventually moving completely into the Cloud. A good news story, right?

Well, maybe. There are a few things that could go wrong. Very wrong. Wrong enough to get you fired. Most of these things have multiple precedents, some of them quite recent. They are realistic concerns and it’s not really plausible for anyone with any knowledge of the past to argue that they won’t happen in the future. I have grouped these concerns into five categories:

Impermanence. The vendor stops providing the service. There are many possible reasons for this happening. Computing is full of product failures and withdrawals. Autodesk alone has such a long history of dead products and orphaned customers, that it would be a major undertaking just to document them all. If the product’s not making money, it’s unlikely to have a future. The vendor itself could go down the tubes. Computing history is littered with the corpses of once-dominant companies. Because there is a chain of dependencies in a typical Cloud solution, there are several potential points of corporate failure. Maybe Autodesk doesn’t go down, but Amazon does, or Citrix. One day, your software just isn’t there any more. What now?
Price ramping. Once you and enough of your fellow customers are tied in, there is nothing to prevent the vendor from racking up the prices. Autodesk has already done this kind of thing with upgrade pricing and Subscription, so it’s not as if it’s an unlikely scenario. If the boil-a-frog-slowly approach is used and you’re the frog being boiled, you’re better off not being tied down when you decide it’s time to get out of the water.
Unwelcome terms and conditions. The terms and conditions under which you operate are often in the Cloud themselves and can be changed by the vendor without you having any say in the matter. What if one day your company lawyer spots a clause has been added that is totally outrageous (even more than normal, I mean) and there is no way your company can possibly continue to operate under those conditions? Good luck trying to negotiate your way out of that one from a position of weakness.
Unwelcome technical changes. I intend to cover the issue of as-you-go upgrades more fully later, but let’s say the vendor introduces a new feature that seriously impacts your ability to use the software productively. No off switch is provided. Sound familiar? It happens to standalone software. It will happen to your SaaS choice, too.
Ignoreware. Your once-fashionable product stops being The New Black. The vendor decides to concentrate its resources in other areas to attract new customers rather than the ones it has already tied up. While your SaaS product continues to be provided, it is put into maintenance mode and nothing useful is added to it. As the rest of the computing world moves on, your SaaS product does not. Holes start to appear that make your life difficult or impossible. Again, Autodesk history is replete with examples of this kind of thing.

If you’re using standalone software and any of the above occurs, it’s probably a pretty big deal, but you can work around it in the short term by simply continuing to use the product that works. You can keep doing this into the medium term, perhaps for several years. Sure, if Autodesk goes down you’ll find that you can no longer authorise new installations or transfer software from one computer to another. But you’ll have some breathing space. You’ll still have all your data, bang up to date. You’ll be able to continue working productively while you look around for an alternative.

If you’ve deeply committed your company to a Cloud solution and the SaaS hits the fan, it’s more than a big deal. It’s a disaster. It could kill your company. It could kill your career. As a computer once asked me, “Do you really want to do this?”

AutoCAD 2012 – Autodesk adds an uninstallation analgesic

1 Reply

One of the more painful aspects of dealing with installations of recent releases of AutoCAD and related products is that although you might run a single setup routine to install what you think is a single application, the end result is a mass of different components being installed. Each of these components is considered a separate program by Windows, and needs uninstalling separately. Frankly, this is manifestly antisocial behaviour.

I have complained to Autodesk about this ever since it started happening, but the number of sub-installations has been getting greater rather than smaller. Now Autodesk has provided an uninstallation tool, which you can find here. If you download and run psebuninstalltool.exe, you will be provided with a list of applications to uninstall.

This is a move in the right direction, but it’s still far from ideal. You still have to choose which applications to install and which to leave alone because they’re in use by some other application, and because of the possible complexities you’re not likely to know. Get it wrong and you can break other applications in a way that’s not immediately obvious. Also, it uninstalls English language products only and is provided “as-is” as an unsupported tool.

This is a welcome kludge to help with a problem that shouldn’t exist. Users simply shouldn’t have to deal with this nonsense. If you install one application, you should be able to just uninstall one application and it should be gone, without breaking anything else. Autodesk, thanks for this interim assistance, but I look forward to the problem being removed in future releases, rather than partially patched over.

AutoCAD 2012 – Autoloader mechanism for plug-ins

16 Replies

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 don’t have to use it, but those who do, and their customers, will have certain advantages. I have used it for the ClassicArray loading mechanism, and I expect to see it used by more and more plug-ins over time. It works fine with all of the usual AutoCAD add-on APIs, including LISP.

User perspective
As a user, what this means is that for AutoCAD and related applications from 2012 on, there is a standard loading mechanism for plug-ins. The installation should be straightforward, with no multi-step processes to go through for different AutoCAD variants and releases. The result of the installation should automatically present itself in a standard way, with a short-lived welcome bubble, an extra panel in the new Plug-ins Ribbon tab, plus any other interface additions the developer wants to provide. If you subsequently install another AutoCAD variant or release, the plug-in will automatically appear in that variant with no further user action required, as long as that AutoCAD variant is supported by the plug-in.

Developer perspective
What this means for me as a developer is that I have much less to worry about in terms of installation. All that needs to be done to make the loading happen is for a folder full of ‘stuff’ to be copied into a certain location. (There are actually two possible locations, but more on that later).

In Betas of ClassicArray, I just provided the folder, plus instructions that asked the user to copy that folder into place. I could have simplified that further by providing batch files that did the copying. In the end, I created setup executables using the free Inno Setup utility, but that was a much easier job that it would have been if this Autoloader mechanism didn’t exist. I didn’t have to worry about discovering what releases were installed, deciphering Registry entries, creating user installaton scripts, or issuing instructions to users to edit files or mess with the AppLoad command. I don’t have to worry about what happens if the user subsequently installs another AutoCAD variant.

Of course, for developers who support releases prior to 2012, there is no less work to do than before, and some time needs to be spent to learn and implement the new mechanism. In the case of ClassicArray, that was not an issue because it’s only needed and supported in 2012. I expect this is one of those problems that will resolve itself over time as developers adopt the new mechanism.

The bundle folder
So what is this ‘stuff’ that needs copying into place? It’s called a bundle folder. It’s just a folder with a name that ends in .bundle (e.g. ClassicArray.bundle), and it typically contains the usual files needed to run your add-in, often tidied up within other folders. The only new thing that it needs to contain is a file called PackageContents.xml. That XML file is the key to the Autoloader mechanism. AutoCAD finds the file, reads it, and acts accordingly in terms of version support, loading program files, partial cuix files and so on.

Bundle folder location
So where does this folder with its XML file have to go? There are two possible locations. If you want the plug-in to be available to all users on the computer, you place it in the Autodesk\ApplicationPlugins folder underneath the system’s ProgramFiles folder. For example, ClassicArray usually gets put here:

C:\Program Files\Autodesk\ApplicationPlugins\ClassicArray.bundle

If you only want the plug-in to be loaded for the current user, it goes in the Autodesk\ApplicationPlugins folder underneath the system’s AppData folder instead, for example:

C:\Documents and Settings\[login]\Application Data\Roaming\Autodesk\ApplicationPlugins\ClassicArray.bundle

in XP or

C:\Users\[login]\AppData\Roaming\Autodesk\ApplicationPlugins\ClassicArray.bundle

in Windows 7.

Describing the contents of that all-important XML file is beyond the scope of this post, but I may do a follow-up post if there is enough interest. In either case, the reference material is available in the AutoCAD Help, under Help > Customization Guide > Introduction to Programming Interfaces > Install and Uninstall Plug-In Applications > PackageContents.xml Format.

Dealing with blacked-out leader plots in older AutoCAD