DWGdirect Overview ODA World Conference 2009 Leiden, The Netherlands Sergey Slezkin DWGdirect Development Team Lead

Early C++ Development Goals Replace OpenDWG Toolkit/Viewkit ASAP. Provide API instead of direct access to all data in C structures. Implement commonly required functionality inside the libraries making them more user friendly. Provide extensible architecture able to incorporate new functionality and features.

Direct Access to Data without Error Checking Not bad for read-only access. Modifying data or creating a new drawing required deep knowledge of data structures and relationships between objects. High risk of writing invalid file which cannot be loaded by any application – loss of data.

Extra Functionality Added at Early Stage Conversions to/from different DWG/DXF versions and taking care of round-trip data through minor versions. Repairing corrupted files and auditing in- memory data. Building dimension blocks, blocks representing standard arrowheads, etc.

Conversions to/from Different DWG/DXF Versions Supported versions: Release 2.5 up to format support to be released later this year. While file loading, drawing is always converted to the latest version. Round- trip data is processed. Client code always works with latest version. While saving, DWGdirect takes care of how new entities/properties should be saved.

Recover — We Did It From: Sergey Slezkin Sent: Monday, September 21, :27 AM To: 'OpenDWG' Subject: Duplicate handles in R12 DWG Hello! I came across a DWG file created by some old version of VisualCADD. It has duplicate handles in entities section and ODT refuses to load it. AutoCAD loads this file. It's RECOVER command reports that it replaced the duplicate handle. Can ODT behavior be changed to be the same as AutoCAD's? Thanks, Sergey Slezkin From: "OpenDWG Alliance Support“ To: 'Sergey Slezkin‘ Sent: Monday, September 21, :26 PM Subject: RE: Duplicate handles in R12 DWG Hi Sergey, Well, this is an Alliance, and you guys have the source code, so if you want write a "RECOVER" utility (and I doubt that when ACAD loads the file it replaces the handle; I think ONLY "RECOVER" does that), please do so and submit it so that others can use it also. It's not something I am going to take on. Sincerely yours, M.R.

Defects that DWGdirect Repairs Corrupted data inside an object (object can be skipped) Missing Table or Dictionary entries (Linetype ByBlock, ByLayer, Style Standard, etc.) Values of system variables Values of various entity properties (such as text’s oblique angle, zero-length normal, zero scale, etc.) Invalid or duplicate handles Cyclic block references Invalid characters in names And more

Some Examples of Error Messages for Entity Containers “Cross references in entities list” “Multiple entries of reference” “Last entity does not match last reference in container” “Invalid subentity type” “Invalid vertex index” “Polyface Mesh has no valid faces” “Polyface Mesh vertex after face” There are more than one hundred different error types which are detected and fixed.

Advanced Functionality Added Undo/redo and transactions support Partial file loading and paging objects Custom object and command plug-ins Protocol extensions Event notifications ACIS support Support for on-screen editing Export to DWF, SVG, PDF, SAT, HSF, etc. DWF and DGN underlay support

DWGdirect Usage Areas Simple DWG processing utilities Import/export plug-ins for CAD applications Visualization Redlining Full CAD applications using DWGdirect as the core

Support Support is performed by developers. Members take advantage of professional answers. Developers directly contacting clients get better idea of problems clients have. Everyday contacts with members help setting priorities for future development.

Supported Platforms Windows 32-bit Windows 64-bit Windows CE SGI Macintosh Linux Solaris HP IBM AIX Windows 32-bit compilers: -MS VC 6 -MS VC MS VC MS VC MS VC Borland Builder 6 -Borland Builder Borland Builder 2009

Customizing DWGdirect Optimize application size by not including optional modules Provide custom implementation for replaceable functionality Add custom functionality (commands and objects) up to creating custom vertical applications

Core Functionality Database General Structure Visualization Interface Rendering Devices Exports DWG/DXF File I/O ACIS Solids Support Other Optional Modules

Optional Modules Rendering devices Enablers for Inventor and MDT entities ACIS support Exports (DWF, SVG, PDF, HOOPS, STL, …) DGN & DWF underlay support DWF import Dynamic blocks Old-styled materials (AVE) support Fields evaluation Plot styles support Raster files support Dimension blocks recomputing Grip/stretch/snap points support OLE support

Alternative Implementations Provided by ODA Rendering devices (WinGDI/OpenGL/DirectX/Bitmap) ACIS support (in-house/Spatial ACIS) Raster support (in-house/JPEG-6B/Snowbound) TTF support (Windows API/FreeType)

Rendering Devices Visualization Interface DirectX DWGdirect Core OpenGLWinGDIBitmap

ACIS Support Modeler Interface Pure In-House Implementation Rendering / Read / Write / Convert / Limited Creation DWGdirect Core Spatial ACIS Full Solid Modeling Support

Raster File Handling Raster Services Interface Pure In-House Implementation BMP files support Implementation using JPEG-6B BMP & JPG files support Implementation using Snowbound Multiple raster file formats support DWGdirect Core

True Type Font Support Font Engine Interface Implementation using Windows API DWGdirect Core Implementation using FreeType library

DWG Functionality DWG Database General Structure Visualization Interface Rendering Devices Exports DWG/DXF File I/O ACIS Solids Support DWF Underlay Support

General Structure Visualization Interface Rendering Devices Exports ACIS Solids Support DWF Underlay Support

Universal Viewer / Converter Visualization Interface Rendering Devices Exports DWG DWF ACIS Parasolid DGN

Conclusion DWGdirect is a powerful cross-platform tool for any DWG processing application development — from simple utilities to full CAD applications. Its flexibility and extensibility provide great opportunities for customization to meet specific needs. Man-years put into its development save a lot of effort for all ODA members. Functionality initially developed as an optional part of DWGdirect can be used outside of it to support other file formats.

Questions