Bricscad™ V6 for Linux

Bricscad™ V6 for Linux is a clone of the widely used AutoCAD®. It uses DWG as its native format.

Supported configurations:

• Pre 6-0-0016 : Fedora Core 1,2,3 with Gnome and KDE.
• 6-0-0016 : Fedora Core 1,2,3, Mandrake 10.1, Suse 9.3. Fixed problems with KDE window handling.
• 6-0-0018 compatibility with WINE 0.9 and later. Runs on most systems. Delivered as RPM and as tar(for Debian-Ubuntu). Does not work with wine 0.9.18. It is possible to patch this however. libwine_unicode.so.1 has been merged with library libwine.so.1, so libwine_unicode.so no longer exists. It is possible to make the application work by creating a symbolic link libwine_unicode.so.1 that points to libwine.so.1.
• 6-0-0020 compatibility with wine 0.9.18 and later. upgraded compiler to gcc 4.1. Runs on Fedora core 5 and 6. In order to run on older linux distributions libc has to be upgraded (from 5 to 6). Please note that this is a critical upgrade and a failure will break many applications.

Please report any problems to www.bricsys.com.

The Bricsys website also contains tutorials and instructions on how to use Bricscad V6.

Version 6.0.0020-1

1/03/2007 

Fixes

• Viewport's off status is lost when switching between layouts
• DimensionSettings/DrawingSettings dialogs. User can't enter values manually to edit controls
• Miscellaneous fixes for printing and print dialog.
• patched wine file wineps.drv.so that uses rounded caps for printing. To apply the patch backup the original wineps.drv.so and replace it with the patched version.

Version 6.0.0019-1

23/01/2006 

Fixes

• Removed a redundant linking dependency. This should avoid a crash on startup across a wide range of linux distributions.
• Fixed a crash on using command saveas.

Version 6.0.0018-1

3/01/2006 

Improvements

• Changed the linking mechanism. From now on Bricscad requires Wine version 0.9 and later. It will not work on Wine versions older than september 2005. Wine 0.9.2 and 0.9.4 are recommended as of this date.
• Changed creation and placement of logfiles. Logfilenames are now created automatically and are no longer editable. The default path for a logfile is the user folder, no longer the program folder. This avoids problems with access rights. A new logfile is created for each drawing.
• Various speed improvements on regen, redraw and on saving.
• Startup script 'icad' now disables UTF for text(see environment variable 'LANG') for the Bricscad session, because UTF causes wrong display of special characters.

Fixes

• Instabilities with the dimensions dialog.
• Repaint problems with combo's in dimensions dialog.
• Lineweights were incorrectly saved in CTB files.
• Real-time operation for a view could start before the previous one was finished. This broke the undo stack.
• Snap and window selection were lost after autosave or setdim dialog.
• Lisp cond function evaluated condition twice in sequence.
• Crash on closing document after removing all entities from pspace layout.

Version 6.0.0016-1

9/09/2005  

Fixes

• Floating toolbars would hang Bricscad with KDE on Suse and Mandrake. This is fixed. The size of the toolbar can still be wrong however.
• Color printing resulted in wrong colors on paper.

Version 6.0.0015-1

19/08/2005  

Fixes

• Licensekey was no longer accepted since WINE version of July 2005. 

Version 6.0.0014-3

26/07/2005  

Fixes

• Removed unnecessary dependencies from licensemanager3.dll and libmfc42.dll. This should solve some installation problems.

Version 6.0.0014-2

14/07/2005  

Fixes

• Added automatic generation of trial key.

Version 6.0.0014

05/07/2005  

Fixes

• Renamed ProfilesEditor to UserProfileManager.
• Path to temporary files folder was not initialized correctly, which caused some save operations to fail for non-admin users.

Version 6.0.0013

01/07/2005  

Installation

• It is necessary to install WINE beforehand. Please use a WINE version between may and august 2005. This build of Bricscad is not compatible with WINE of september 2005 or later. If you want another user to be able to run Bricscad make sure the user has setup wine. The wine setup is stored in /home/username/.wine, in the files config, system.reg, userdef.reg and user.reg. Bricscad does not need any special configuration settings in order to start.
• If the Bricscad version 5.1.0012 is present then it is necessary to uninstall it before installing the new version. Otherwise the program will crash on startup.
• The program is installed in /opt/Bricscad.
• The RPM installs a launcher icon in the menu. The icon is located in the root menu or in de Office submenu. If necessary you can add your own launcher icon by pointing to /opt/Bricscad/icad. You can use the icon /opt/Bricscad/Bricscad.ico.
• The installer creates an evaluation license for the user who runs the installer, which is usually root. When starting Bricscad the first time as a normal user, the program will not find the evaluation key and will ask for the licensekey. WINE can be configured to share the 'system' part of the windows registry between users. Otherwise only the root user can evaluate the program.
• The installer does not handle file associations (the doubleclick behaviour on a file in your filebrowser).
• VBA is not present. COM is present and will work as much as WINE supports it.
• TrueType fonts are supported but not delivered. Either you should add the fonts yourself, or create a fontmap icad.fmp to map these fonts to TrueType fonts that are already on your machine.
• The options dialog > paths tab has 3 extra fields:
  
  - One to select a native (Linux) web browser. This enables the command URL and hyperlinks.
  
  - The next path is for a native file viewer, enabling the commands PLOTTERMANAGER and PLOTSTYLEMANAGER. For these commands to work properly, the options > paths dialog must have the plotstyles and plot configuration paths pointing to the correct folders respectively the 'Plot Styles' and the 'Plotters' folders.
  
  - And another path for a PDF viewer, enabling the command HELP. The CHM files have been delivered also, but any available viewers that we know of ignore the linking between the CHM files, which makes CHM files harder to use.

Remarks

• We support this version on Redhat 9 and Fedora Core 1,2 and 3, under Gnome and KDE. We're making final corrections to support Suse 9.3 and Mandrake 10.1. Other distributions will follow shortly.
• This version was built on Linux with WINELIB. The names of the binary files have changed. Instead of a file xxx.dll(example gr.dll) there are now binaries xxx.dll.so(gr.dll.so) and symbolic links libxxx.dll.so(libgrdll.so).
• This version has limited extensions. XRM, imagemenu, userprofilemanager and access to DWG2004 format are present. QRENDER and viewing/editing of 3D solids, will be reintroduced soon. Raster support is uncertain. The RENDER module will not be ported from windows.
• Apart from the extensions, the functionality in this version is the same as in our Windows V6 version.
• This version is no longer compiled on windows. It is compiled on Linux with GCC 3.3.2. The names of the binaries have changed. Instead of a file xxx.dll (gr.dll) there are now binaries xxx.dll.so (gr.dll.so) and symbolic links libxxx.dll.so (libgr.dll.so).
• This version has limited extensions. XRM, imagemenu, the UserProfileManager and DWG format 2004/2005 are present. QRENDER and viewing/editing of 3D solids, will be reintroduced soon. Future support for images is not certain yet. The rendering module will not become availabe on Linux.
• The MTEXT editor is partly functional and not stable. It is possible to use an external editor that runs under WINE. The system variable MTEXTED controls this.

Known Problems

• XRM dialog, attach dialog, can cease to react in some cases. The dialog can then be closed with the X button top right of the window, and Bricscad will continue to work, but the XRM dialog will be unusable for the rest of the session.
• Opening files of DWG 2004 format crashes on some machines.
• The mtext editor is partly functional and not stable. It is possible to use an external editor that runs under WINE. The system variable MTEXTED controls this.

Performance Tips

• Stretching and moving the main Bricscad windows is slow. It helps to switch off redrawing content on moving and resizing. Some window managers allow you to suppress redraw during drag. It's possible in the interface of KDE, but not in basic GNOME. An additional window manager is needed to control this. Candidates that support this feature are Sawfish, Icewm and Twm.
• Please keep the thickness of the flyover snap marker equal to 1. Thicker snap markers (the windows default is a thickness of 2) cause a significant performance cost.

Copyright

Copyright IntelliCAD Technology Consortium.
Portions copyright Visio Corporation.
Portions copyright Bricsys nv.
All rights reserved.

This program is protected by U.S. and international copyright law as described in the license agreement.

Bricsys nv

Bellevue 5/201
9050 GENT
BELGIUM