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.

One Comment:

  1. I think that’s (along with the (afwul, IMO) ribbon) a problem of Autode$k being married too tightly with Micro$oft, and the move away from good old ‘HTML Help’ must have been related to MS intent to scrap it, but finally left it undead, too late for Autodesk users (same happened to VB, etc…).

Leave a Reply