Tag Archives: Review

BricsCAD documentation – a tale of three systems – part 3

In this third post in what was supposed to be a two-part series, I have more to say about the BricsCAD documentation system. See here for part 1 and here for part 2.

Developer Help – Addendum

In this comment from Bricsys API person Torsten Moses, he informed me about the availability of the Lisp Developer Support Package (LDSP) in the Bricsys Application Catalog. As always, when presented with new evidence I am prepared to re-examine my position on anything. Therefore, I will now further discuss the BricsCAD developer documentation.

The first thing to mention is that the existence of the LDSP package is not obvious. To somebody who uses BricsCAD as-provided and as goes burrowing down through the Help system looking for information, that system is still broken. The documentation as presented to the user remains sub-standard, exactly as described in part 2.

Assuming you know of the existence of LDSP, how do you go about using it? Here are the steps:

  • Go to the Bricsys Application Catalog site, click in the search field and start typing LDSP (you don’t need to hit Enter).
  • The link to the Lisp Developer Support Package (LDSP) will appear: click that.
  • Enter your email address, accept the privacy agreement and pick Download. (Note in passing that this is actually published by Torsten’s own company, not Bricsys).

  • If you’re already a registered Bricsys user (you will be if you’re evaluating it), the download will start. If not, you’ll be expected to register (free):

  • Once you’re registered, the download results in a 12 MB file called Lisp Developer Support Package.rar (RAR is a ZIP-like format).

Any recent commercial ZIP utility (e.g. WinZip) will open RAR files and there are a variety of freeware/adware/shareware utilities available to do likewise. For example, RAR Opener in the Windows Store will present itself as the first option in Windows 10. But it goes without saying that going off in a hunt for utilities wouldn’t be on anyone’s expected to-do list when just looking for product help. A bunch of people would give up here, if not earlier.

I went through with installing RAR Opener, but when I attempted to open the LDSP file I saw this:

Oh, and a handful of empty folders were produced. Is there an email waiting for me at work with the password (my Bricsys registration email is at work but I’m at home)? Am I really supposed to have a password to open this RAR? If so, why wasn’t I prompted for one? RAR Opener doesn’t present me with that option anywhere I can see. Is the download corrupt? Does it refuse to work on a Sunday? I have no idea.

At this stage, many more would give up. How many prospective customers would be filtered out by this experience? There’s no way of knowing. However, I’m made of sterner stuff and persevered with downloading and installing another app from the Windows Store. 9 zip did the job and uncompressed the file, no password required.

Yes, the RAR Opener problem I had above isn’t a Bricsys problem directly. But it is indirectly, because the file I was given to deal with won’t open by default in Windows, where the vast majority of BricsCAD users will be working. It’s a level of obfuscation that you can get away with when dealing with cellar-dwelling geeks handling obscure pieces of open source software. It’s not appropriate for customer-facing documentation in a mainstream CAD application. Yes, even developer documentation, because with CAD applications like AutoCAD and BricsCAD, most of the developers are customers/users/managers, not people trying to sell utilities.

Once you manage to get the file uncompressed (it becomes 41 MB), there are three help systems provided in there (CHM, PDF, HTML). That’s excellent, and conforms nicely with the Bricsys philosophy of providing customers with choice. I was unable to find any broken links. However, even in the LDSP, standard AutoLISP functions are undocumented. So I still couldn’t find the (entget) help I was looking for in part 2:

According to Torsten:

…the standard AutoLISP functions like (entget) are not documented, as there are plenty docs on the web for this; but we document any extension beyond AutoLISP standard, even for the standard functions.

Sorry, but while “we don’t have that information but you can Google it” might have been an acceptable answer for a cheap AutoCAD clone’s API documentation ten years ago, that’s not where BricsCAD is today and most definitely where Bricsys wants it to be in future. Just two days ago, Bricsys CEO Erik De Keyser sat across a table from me and told me that BricsCAD isn’t intended as merely an AutoCAD alternative, but must go well beyond that in order to prosper. He’s right. The BricsCAD developer documentation today is not compatible with that vision. I know it’s that way for historical reasons, but we’re now at a different point in the historical timeline.

Conclusion – Addendum

My conclusion from Part 2 remains valid, despite the existence of LDSP. Both Autodesk and Bricsys have work to do. Downloading LDSP will help with some of the BricsCAD developer documentation failings but leaves plenty behind. It also provides its own set of unfortunate challenges.

This isn’t just a technical and ease-of-use failing, it’s a marketing one. That’s because it acts as a stumbling block to conversion of AutoCAD sites to BricsCAD. Disaffected AutoCAD power users in small sites and CAD Managers from large sites are right now taking tentative steps to evaluate the suitability of BricsCAD to replace AutoCAD in their complex LISP-heavy custom environments. They’ll want to know what’s the same and what’s different so they can estimate the effort and cost involved in the transition before getting in too deep. I know this, because I’ve done it myself. The first thing they will come across in their search is disjointed, very inconvenient and incomplete. It presents a less-than-professional image.

Some potential customers, like me, will persevere and discover that the quality of the developer tools implementation far exceeds the expectation generated by the documentation. Others will give up well before they reach that stage, and that’s a shame.

BricsCAD documentation – a tale of three systems – part 2

In this pair of posts, I describe the BricsCAD documentation system. Click here for part 1, where I describe the general Help system and the descriptions in the Settings command.

In this part, I discuss developer documentation and draw my conclusions.

Developer Help

If we count the Settings descriptions as a system, there’s a third documentation system for BricsCAD. The Developer Reference isn’t offline and included in an install like the main Help. Instead, it’s online, just like Autodesk’s default. Unlike Autodesk’s system, it works pretty well.

Being online means the performance suffers, of course, but it’s generally not too bad. It appears quicker than Autodesk’s. A link within the main Help system takes you to the Bricsys Developer Reference which is just accessed using your default browser. Of course, that means your mouse buttons work correctly and you have all other the advantages of whatever functionality is built into your browser.

Hot tip: you can get to a real browser from within the AutoCAD pseudo-browser thing too, by right-clicking on a link and picking Open in Browser. The URL takes a while to mangle and unmangle itself before you get to read any content, but you get there in the end.

Unlike the general Help, the BricsCAD developer Help system isn’t so obviously superior to its AutoCAD equivalent. This is largely thanks to the outstanding efforts of Autodesk’s Lee Ambrosius who has managed to take Autodesk’s pig’s ear of a system and produce perhaps not a silk purse but at least a decent-quality cloth bag. It can’t have been easy.

Like the main Help, the BricsCAD online developer reference has a Contents mode with structure:

There’s an Index:

And there’s Search:

As the last image shows, the system contains not only missing information (where’s the (entget) description?) but also broken links; this wasn’t the only 404 I came across. That’s a bit embarrassing, Bricsys. There’s a lot of work to be done yet to bring this up to scratch.

There’s no Favorites section, but of course that’s built into your browser so it would be pointless reproducing that.

Of course, you can’t get context-sensitive help on functions within your LISP code from VLIDE, because BricsCAD has no VLIDE.

Conclusion

The BricsCAD documentation system is notably better than the AutoCAD one in many ways. However, it’s a long way short of perfect. Many aspects need attention, and there are multiple holes to be filled. Sometimes I find myself forced to use AutoCAD’s general documentation system to find out something about a system variable that’s common to both systems. That shouldn’t be necessary.

I’ve hardly mentioned the content of the respective documentation systems, but I must say Autodesk’s content is often superior (thanks, Dieter). But there are exceptions; the BricsCAD descriptions and pictures of various commands and options are better in some cases. For example, try to find out what the various options of the PEdit command do in both systems. With BricsCAD, it’s all laid out on one page and nicely linked.

The AutoCAD command documentation has been pared down too much in places to make each page shorter and simpler, hiding the content beneath sometimes obscure links. It’s possible to find out what the Pedit options do in AutoCAD, but it’s certainly not BricsCAD-easy and I initially gave up after chasing my tail for a while. I went back and found it later, but it took a lucky guess. Giving up after looking through a circular set of links is a common experience with AutoCAD’s Help. There’s a programming concept called mutual recursion, but I don’t want to experience it during a vain search in a Help system, thanks. A visible, navigable structure would help eliminate that issue, but there isn’t one. There needs to be one. Did I mention that already?

With system variables, BricsCAD’s Help is consistently and clearly inferior to AutoCAD’s. The AutoCAD content also tends to be better worded, with the BricsCAD wording being occasionally slightly awkward in a non-native-English-speaking manner. There are also some formatting issues with wide gaps left where the system attempts to expand command descriptions to the right margin and does a poor job of it.

As with AutoCAD, there are many video tutorials available for BricsCAD. I have not considered these in my evaluation but the few I had a look at were pretty good.

Who wins? Nobody. It’s a draw. Both companies need to step up. Autodesk mainly with its awful structure-free system, Bricsys mainly with its incomplete content, particularly for developers. But both companies have work to do in all areas.

BricsCAD documentation – a tale of three systems – part 1

Because of the great similarity between BricsCAD and AutoCAD in terms of commands, variables and most aspects of usage, you would expect the BricsCAD documentation to be about the same too. But it isn’t. Much of the content covers the same areas and due to BricsCAD’s command-line compatibility, there must be a lot in common. But the Help system is very different from Autodesk’s. How so?

In this pair of posts, I describe the BricsCAD documentation system. I assume you’re familiar with the AutoCAD one. In this first part, I describe the general Help system and the descriptions in the Settings command. In part 2, I will discuss developer documentation and draw my conclusions.

General Help

The general Help system in BricsCAD looks a lot like the excellent CHM-based system that AutoCAD had in 2010 and earlier (thanks, Dieter). BricsCAD’s Help is offline by default, included with the standard download and installation, and very fast. Those are great things to have, and AutoCAD lacks them all. But the great thing about the BricsCAD Help system is that it supports different usage patterns, rather than Autodesk’s search-or-nothing method. Rather than telling users that they are expected to use Help in one specific way, Bricsys accommodates their disparate wishes. As usual, the customer-friendly way is the winner.

The BriscCAD system looks a lot more old-fashioned than the AutoCAD one. I don’t care about that. I do care about space-efficiency though, and BricsCAD is the winner there. You can of course resize the dialog and the size of the left pane.

There’s a Contents tab which allows you to navigate the hierarchical structure in which the information is arranged. That’s useful not only when looking for something in particular, but also when using the system as a self-teaching mechanism by working through an area and related topics. AutoCAD completely lacks such a structure.

There’s an Index tab that lists the indexed items in alphabetical order. You can start typing and the indexed items instantly change to reflect what you’ve typed, which is much more efficient than Autodesk’s system. AutoCAD 2018 Help does include an alphabetical list of commands and system variables in both online and offline versions, but it doesn’t give access to all of the topics.

There’s a Search tab that allows you to enter a search term and have several suggestions thrown up. Unlike Autodesk’s system, the suggestions are displayed in a space-efficient manner. Unfortunately, like Autodesk’s search, the suggestions displayed often differ from what you’re after. Even hitting F1 within a command doesn’t take you straight to the page for that command. In PEdit, the F1 visible suggestions don’t include the PEdit command page! It’s there, but needs a scroll down. That really needs work.

There’s also a Favorites tab where you can save and restore any pages you want to go back to.

But that hierarchical structure is the big winner. Destroying that structure in the AutoCAD 2011 pseudo-browser Help debacle and leaving it broken for seven further releases has to rank among the silliest self-destructive acts Autodesk has ever performed on AutoCAD. Because Bricsys never made that mistake, its general Help system is superior to AutoCAD’s. Until Autodesk throws away its flat-structure mindset and starts again, it has no hope of catching up to the BricsCAD system.

Oh, and your mouse’s forward and back buttons work in the BricsCAD system. How long have we been nagging Autodesk about that? Seriously, how hard could that be?

It’s not all good, though. As mentioned at the top, the AutoCAD content is generally superior. There are also quite a few holes. Enter a system variable at the command line and hit F1. You would expect to get context-sensitive information about that system variable. You don’t. You’re just taken rather uselessly to the “Welcome to BricsCAD” page. This needs attention to ensure context-sensitive help is available for all commands and system variables.

Fire up Help, pick the Index tab and start typing in a system variable name. In most cases, you’ll find it’s not in the list (e.g. FILEDIA). In cases where a system variable name does appear in the list (e.g. FILLMODE), double-clicking on it doesn’t take you to a description of the system variable. Instead, you will be presented with multiple topics and it’s often not clear which is the system variable description.

Settings Descriptions

For system variables and most other settings, you’re better off avoiding the main Help system altogether. Instead, use the Settings command. This is like Options in AutoCAD but superior, because it’s all there and arranged much more logically. You can navigate a hierarchical structure to find the setting you want, but you can also type part of the setting name or a related word into the search box at the top of the dialog. If that doesn’t take you immediately to the setting you’re after, you can use the up and down arrows to go to the next match. It’s all very quick and efficient.

Unlike AutoCAD’s Options, you don’t need to go hunting from tab to tab, visually scanning the dialog for the setting you want, which might be hidden under a button or not there at all. Also far superior to AutoCAD, the descriptions don’t hover over the dialog, obscuring what you’re looking at. Dieter has been hacking the AutoCAD dialog hover-tips down in size for years, but they still annoy the heck out of me until I turn them off.

When you find the setting you’re after, a brief description is displayed at the bottom of the dialog. In most cases, this has just the right amount of information you need without having to read through a whole page. If it doesn’t, in some cases it will tell you the setting name. However, this is missing in many cases.

This is a “could do better” area for Bricsys. Somebody needs to go through these descriptions, fill the holes (not a small job) and make them all consistent. While they are at it, get them to tie up all of the missing context-sensitive loose ends in the main system. Better still, provide a button or other method within Settings to take the user to the appropriate Help page. Currently, pressing F1 within the Settings command will give you useful but generic information about using the dialog. Unfortunately, it will not give you information about the setting you want to check or change. That needs to happen.

Click here for Part 2.

Autodesk updates Design Review

Despite the previously announced end-of-active-life for Design Review (Autodesk’s DWF viewer), there is now a new release available. This wasn’t supposed to happen, because we should all now be using cloud-based solutions.

A new version of DWG TrueView was needed to deal with the new DWG 2018 format, and one knock-on effect is that a new Design Review was needed to be compatible with DWG TrueView 2018.  It’s still only 32-bit, so it appears to be a matter of Autodesk just touching it up enough to keep it compatible.

Interestingly, the new Design Review is not called 2018. Here’s where to find it:

On the bloatware theme, if there’s a particular reason this download (421 MB) is over eight times the size of its predecessor (49 MB), it’s not readily apparent.  The installed application is 212 MB, so it’s all a bit mysterious.

The downloaded executable is a WinZip self-extractor. If you’re a CAD Manager, there’s no point in having the unzip happen 100 times for 100 users when it could happen just once, so you’ll want to grab the extracted files and install from those. This installer makes that difficult, but not impossible. If you want to do that, read on. If you’re just installing it once, skip the next two paragraphs.

Running SetupDesignReview.exe (note the lack of version information), the extraction started but I couldn’t find out where it was extracting to. I eventually found it in the folder %Temp%\XXX.tmp, where XXX is a random name, e.g. _AID0D9. This folder gets automatically erased on completion or cancel, so what you need to do is run SetupDesignReview.exe once, wait for the unzipping to finish but don’t go ahead with the install, copy the %Temp%\XXX.tmp folder elsewhere, then cancel the initial installation. You can then run as many installations as you like using the extracted files.

It would be useful to have these things documented. The Installation Help, System Requirements and Readme links in the installer all rather unhelpfully point to a generic Knowledge Network search.

The install proper will uninstall Design Review 2013 without asking, which is antisocial. For example, if you wanted to keep using HP Instant Printing (not supported in the new release), this installation would mess you up. In my case it also threw up an error during that uninstall, although it still seemed to go through with it.

Note there’s no sign of a release number. The only versioning I can find is in Help > About, with a build version of 14.0.0.177. When you run it, you’ll notice that it hasn’t had the UI of Doom treatment, so it looks like a cut-down AutoCAD from a few releases ago. Not a bad thing.

How about the product itself? Seems to work OK. If you go to open something, it will show you DWG files as well as DWF(x) files. What happens if you try to open a DWG file? This.

Everybody familiar with versioning knows you never put “the latest version” on anything because it’s meaningless. I was once told about a Head Drafter in the early CAD days who had special stamps made up to stamp paper plots with THIS IS THE LATEST VERSION OF THIS DRAWING. The above message is about that smart.

What happens when you pick the Learn More button? Nothing. So I learned nothing.

Anything else? Well, on my system, it takes about twice as long to start up this simple DWF viewer than it does to start up a full-blown CAD application. Want to take a guess at which application I mean?

Can’t complain too much. This product is free, Autodesk is still providing it and still making efforts to keep it up to date. Props for that much, at least.

AutoCAD 2018 – bear this in mind

Given the dearth of new functionality in AutoCAD in recent years, it’s understandable that Autodesk has taken to claiming credit for the same thing twice. The same features have been touted once for the 2017.1 mid-term update and again as 2018 new features. Even I fell for it, listing linetype gap selection as a 2018 feature in my original review.

For the purposes of reviewing the earlier AutoCAD releases and AutoCAD 2018 as upgrades, I have included the 2017.1 features in 2018, not 2017. Some of those features are praiseworthy, and there have been some minor improvements to some of the 2017.1 features in 2018, but let’s count them just once, please.

Blogs and sites that just regurgitate Autodesk’s take on what’s new in AutoCAD 2018 might inadvertently repeat the double-dipping. Bear that in mind when you read reviews.

Let’s have your AutoCAD WS 1.6 reviews

Autodesk has just released the latest iteration of its free online CAD app, AutoCAD WS. It’s available directly via your browser or as iOS, Mac or Android apps. This is the closest Autodesk has yet come to showing us what real CAD in the Cloud can do. Autodesk has now had three years’ work behind it since buying the company responsible for this technology. I’d like you to put aside any Cloud concerns you may have and give it a fair go. Please try it out and report back what you find in a mini-review. How well does it work? The customer stories are all from organisations using it as a viewer or for simple markup edits. Is that all it can do, or does it come close to deserving to have CAD in its name?

What do I want you to try? It’s up to you, but I don’t want to waste too much of your time. Why not have a go at something that would only take you a couple of minutes in any AutoCAD release from the last quarter of a century?

For example, I’m sure everyone here could start a new drawing using a template containing your company’s layer standards, insert a title block and populate a couple of the attributes, then accurately draw and dimension a single 2D view of a rectangular plate containing a single round hole. Try to do the equivalent in AutoCAD WS. If you have difficulty with that, try uploading a simple drawing and perform a few simple edits instead. How did that go?

I’ll be interested to see what you came across at each stage of the process. Was the setup process straightforward? What was easy to do in the WS editor? What was difficult? What was impossible? What worked well? What didn’t? What happened quickly? What took a long time? What’s good about the interface? What’s not? Do the commands work as you would expect them to? Please try to describe your experiences as objectively as you can.

Note: I’ve asked a similar question before, but that was some time ago and things have moved on since then.

Not another SpacePilot PRO review

This post is not about the new SpacePilot PRO 3D controller from 3Dconnexion (a division of Logitech). This post is about the Internet coverage of the launch of that new device, journalism, blogging, freebies and ethics.

It has long been common practice for companies to give out free stuff to journalists. Free gadgets, free transport and other expenses for attending events, free beer, free lunch… oh, wait, there’s no such thing. As blogging has risen in prominence, that practice has been extended to providing free stuff for bloggers. It was traditional in the past for such freebies to go unmentioned in reports about the products of such companies. I think the first time I saw this kind of thing disclosed was by Ralph Grabowski, and I was impressed. Maybe it’s just the sites I read, but I see more of that kind of disclosure in blogs than I do in the traditional press (whatever that means these days).

It seems that 3Dconnexion is distributing its US$499 SpacePilot PRO devices like confetti (particluarly at SolidWorks World), hoping to get as much coverage as it can. It’s working. Not that I think there’s anything wrong with that. If a company wants to let potential customers know about its products, and if those customers read blogs, it makes sense for the company to send samples to bloggers in the hope that they get reviewed. As long as there are no strings attached, I see no ethical problem with that. If a negative review led to a reviewer being taken off the freebies list then I definitely would have a very big problem with that, but I see no evidence of that from 3Dconnexion.

Where I do see an ethical issue is when a freebie is received, a review is written, and no disclosure is made. I think readers are entitled to know about any free stuff associated with a review, and I think this applies equally to press and blogs.

Let’s have a look at some recent SpacePilot PRO coverage to see how we’re travelling at the moment. The following sites have mentions or reports without explicit disclosure. In many cases a mention is made of having one (or waiting for one) but it’s not clear if this is a free SpacePilot PRO, or if the writer has paid for one. If you’re one of these people, feel free to set the record straight either here or on your own site.

Here’s how I think it should have been done:

There are almost certainly other reviews and mentions that I’ve missed, so feel free to inform me and I’ll add to the above lists.

I hasten to point out that I’m not throwing stones here. I’m not accusing any of these people of writing positive reviews in return for a cool gadget. I’m just encouraging everybody to unambiguously declare any freebies they receive, that are associated in any way with whatever they write.

On Twitter, I see several of my fellow AutoCAD bloggers impatiently awaiting the arrival of their cool gadget. When they receive them, I expect we will see more reviews, and it will be interesting to see how many of those reviews include full disclosure, especially now I’ve raised the issue.

Here’s my own disclosure about my personal association with 3Dconnexion. I investigated the use of 3D controllers for a client and suggested the purchase of a couple of pretty expensive 3Dconnexion SpaceBall 5000 devices. Within months of purchase, 3Dconnexion made these obsolete without warning and failed to produce any new drivers for them, making them expensive paperweights.

When I attended AU 2006 (at Autodesk’s expense as a MyFeedback Scholarship), I turned up at the Press Room looking for a Press badge, as I am a Cadalyst writer. I received a Press person’s small bag of assorted goodies from various vendors. This included pens, small USB keys and the like, but a 3Dconnexion SpacePilot was the stand-out freebie. I later suggested that my client purchase a couple of SpacePilots to replace the obsolete SpaceBalls. Not because of the freebie, but because they were the cheapest suitable devices available.

So, on a personal level that’s one up and one down for 3Dconnexion. My view of 3Dconnexion is about the same as that of parent company Logitech. I like the devices, I’ll even use my own money to buy them, but I don’t think a good enough job is done of supporting recently purchased devices with updated drivers as new software arrives.

I haven’t received a SpacePilot PRO or the promise of one. I’m not sore about that. I haven’t asked or been asked. If they do happen to send me one, I’ll play with it and if I think it’s worth writing about, I’ll do so in an unbiased way and with full disclosure.

Why I won’t buy another Canon all-in-one printer

Last year, I bought a Canon MP830 printer/scanner/copier/fax/tea maker/whatever for my home office. I chose this particular device because it had all the features I was after, including CD printing, duplex printing, printing to the edge of the sheet, decent photo printing quality, and great document handling including automatic dual-sided copying. It also had theoretical high speed operation and ink economy with 5 separate tanks. It also looked like a sturdy piece of kit that wasn’t going to wobble all over the place in use, and which might stand a chance of lasting a long time. It was at the upper end of the Canon range, but even then it wasn’t expensive.

I was a little worried that when one part of it eventually failed, I would be stuck with a partially functional device, such as a scanner/fax that wouldn’t print, or a printer that wouldn’t scan, and be left with the dilemma of replacing all of it or part of it. But I had good experiences with long-lived printers in the past (albeit Hewlett-Packard ones), so I figured that if I had to throw it away in five years’ time I could live with that.

In practical use, most of the device’s features turned out to be as advertised, and while it was working I was generally happy with it. But I won’t be buying another one, and it’s unlikely that I will ever buy another Canon printer of any description. Why not?

  • Performance. This simply isn’t up to scratch. While it may theoretically print a 500-page document at 30 pages per minute, printing a single page is a different matter. Although it can look spectacularly quick in action, it takes one full minute from turn-on to get itself ready to do anything at all, then about 10 seconds to print a simple monochrome page in draft. There are also long delays when the device is switching from one kind of use to another. The lengthy period of whirs and clunks indicates that it’s doing something very important internally, but I have no idea what. I don’t care. For my typical use, it’s just too slow.
  • Economy. The ink savings promised by the 5-tank system are illusory. This thing eats ink at a rapid rate, so I’m finding that the costs of running this printer are significantly greater than my previous Hewlett-Packard. Having to maintain at least one spare (preferably more, because they don’t last long) of each tank is inconvenient and means there is always an expensive set of tanks lying around waiting to be thrown or given away when the device finally dies. Which, given my experience to date, could be any day now.
  • Reliability. It doesn’t have this. It had to be returned for warranty repairs in its first year, as it complained about its ink tanks. This resulted in the print head being replaced. Out of warranty, it started doing the same thing again. This was sometimes fixable by various means, such as removing and replacing the tanks, switching the device on and off, removing and replacing the print head, cleaning the contacts, prematurely replacing unfinished ink tanks with new ones, and so on. This would sometimes fix the problem on the first or second attempt, but this level of cooperation didn’t last for ever and the condition gradually worsened until the device was officially dead. I took it in for repair but apparently a new print head (which costs 30% as much as the printer) was not required this time. It has been fixed, for now, by replacing one of the half-full tanks with a new one. Apparently, genuine Canon tanks, which are the only thing it has ever had in it, are prone to bad batches, and I’ve been unlucky. The little chip on each tank, which is intended to make life difficult for makers of third-party tanks, has been making my life difficult instead.
  • Idiotic design. This is the killer. You may recall my concern that I would be left with a partially functioning device when one part failed. I need not have worried about that, because it seems the Canon design philosophy is one of extreme built-in obsolescence. When one part fails, even if it’s just an ink tank, the whole machine is a boat anchor. When the magenta ink tank is faulty, that doesn’t mean your prints come out looking rather less pink than they should. It doesn’t mean that you are restricted to monochrome prints. It doesn’t mean that you can’t do any printing at all. It means that the device is completely, absolutely, 100% useless. You may think that it should be possible to print in monochrome, scan a page, or send a fax without a cooperative magenta ink tank, but the Canon designers apparently think otherwise. What on earth were they thinking? I mean, how could anybody possibly think this is an appropriate design decision? Strewth!

Canon, this device is not good enough. I know that one person’s reliability experiences are not statistically significant, but even without that, the other downsides are enough to make me not want to repeat this unpleasant buying experience.

I have had very long life, 100% reliability and relative economy out of Hewlett-Packard devices in the past, so it looks like I’ll be returning to the fold with my next purchase. I know that HP doesn’t quite have the exalted quality reputation it once enjoyed, but it surely can’t be as bad as this. Can it?