Using DOTNETARX To Develop Your .NET ObjectARX Applications

• Download source files - 229 Kb
• Download demo project - 817 Kb

Introduction

With the newest AutoCAD 2006, the .NET programmers can use the ObjectARX Managed Wrapper Classes to develop their AutoCAD programs. But there are many inconveniences and bugs in the wrapper classes. For example, you cannot do conditional filtering, and many global functions in C++ is not provided in the wrapper class. To solve the problems, I have developed a tool �DOTNETARX� to help the .NET programmers to write the ObjectARX programs more easily.

First, let�s look at the traditional ObjectARX programs written in C#. The following example adds an entity to the AutoCAD.

Entity ent��; 
Database db= Application.DocumentManager.MdiActiveDocument.Database; 
DBTransMan tm=db.TransactionManager; 
using(Transaction trans=tm.StartTransaction()) 
{
  BlockTable bt=(BlockTable)tm.GetObject(db.BlockTableId,OpenMode. ForRead,false); 
  BlockTableRecord btr=
    (BlockTableRecord)tm.GetObject(bt,
    OpenMode.ForWrite,false);
  btr.AppendEntity(ent); 
  tm.AddNewlyCreatedDBObject(ent,true);
  trans.Commit(); 
}

Oh, I have to write so many codes only to add an entity!! Even more, when I want change the property (such as color) of the entity after it is added into the AutoCAD, I must use the same codes to open the entity (using the transaction) and then change its property. Can it be done more easily? The answer is DOTNETARX. With this tool, you can write the above codes like this:

Entity ent��. 

Tools.AddEntity(ent);

Note: To use DOTNETARX, you must add the reference to �DOTNETARX.dll�, and import the DOTNETARX namespace in your source code:

using DOTNETARX;

Now, you only need two lines of codes to finish the same thing! Can�t believe it? It�s true, your work will become simple with DOTNETARX.

DOTNETARX is a .NET assembly with many useful classes. Let�s see the main classes in DOTNETARX.

The most important class in DOTNETARX is Tools. The members of this class are static. It has the following members:

• Properties:
  • Database: gets the current AutoCAD database.
  • Editor: gets the editor associated with the current document.
  • TransactionManager: gets transaction manager of the current database.
• Functions:

  With the three properties, you can replace the long codes such as Application.DocumentManager.MdiActiveDocument.Database with Tools.Database.

  • public static ObjectId AddEntity(Entity ent)

    Adds an entity to the current AutoCAD drawing. The following codes add a line to the database:

    Line line;
    
    ��.
    
    Tools.AddEntity(line);
    

  • public static ObjectId AddSymbolTableRecord(SymbolTableRecord str,ObjectId symbolTableId)

    Adds symbol table records to the current database. The following codes add a new layer to the database:

    LayerTableRecord ltr;
    ��
    Tools.AddSymbolTableRecord(ltr,Tools.Database.LayerTableId);
    

  • public static ObjectId AddDictionaryObject(string searchKey)

    Adds the dictionary object to the current database.

  • public static ObjectId AddDictionaryObject(string searchKey,DBObject newValue,ObjectId ownerId)

    Adds dictionary objects such as XRecords and groups.

  • Functions used to set or get the general properties of an entity:

    The properties are: Color, ColorIndex, Layer, Linetype, LinetypeScale, LineWeight, PlotStyleName and Visible. The name of the function which sets the general properties of an entity starts with Put, and then followed by the property�s name. For example, PutColor is used to set the color of an entity. There are two forms of this kind of function.

    1. The first one is PutColor(Entity ent,Color color), the ent parameter is for the entity, and color is for the color value.
    2. The second one is PutColor(ObjectId id,Color color), the id parameter is for the object Id of the entity, and color is for the color value.

    The name of the function which gets the general properties of an entity starts with Get, and then followed by the property�s name. For example, GetColor is used to get the color of an entity. There are two forms of this kind of function.

    1. The first one is GetColor(Entity ent), the ent parameter is for the entity.
    2. The second one is GetColor(ObjectId id), the id parameter is for the object Id of the entity.
  • public static void Move(Entity ent,Point3d fromPoint,Point3d toPoint)

    Moves an entity object along a vector.

  • public static void Rotate(Entity ent,Point3d basePoint,double rotationAngle)

    Rotates an entity object around a base point.

  • public static void Scale(Entity ent,Point3d basePoint,double scaleFactor)

    Scales an entity object equally in the X, Y, and Z directions.

  • public static ObjectId Mirror(Entity ent,Point3d mirrorPoint1,Point3d mirrorPoint2,bool eraseSourceObject)

    Creates a mirror-image copy of a planar entity object around an axis.

  • public static ObjectId Copy(Entity ent)

    Duplicates the given entity object to the same location.

  • public static void Erase(Entity ent)

    Erases the given entity object.

  • public static Entity GetEntity(ObjectId id)

    Gets AutoCAD entity object by its object ID.

  • public static DBObject GetDBObject(ObjectId id)

    Gets AutoCAD DBObject by its object ID.

  • public static DBObjectCollection GetIteratorForSymbolTable(ObjectId id)

    Gets an iterator. It is used to iterate through a symbol table record.

  • public static ObjectIdCollection GetIteratorForSymbolTableID(ObjectId id)

    Gets an iterator. It is used to iterate through a symbol table record.

  • public static Point3d GetMidPoint(Point3d pt1,Point3d pt2)

    Gets the midpoint of two points.

The other classes in DOTNETARX are derived from the AutoCAD entity classes such as Circle and Line.

By the latest edition of DOTNETARX, I have derived from the following classes:

Line, Circle, Arc, Ellipse, Polyline, DBText, MText, Table, Hatch and the Dimensions. The names of the new classes are their ancestors� name and with appended an �s�. For example, Lines is the derived class of Line. The first purpose of the derived classes is to create entities more easily. For example, you can only use center, radius and vector to create a circle with the original constructor of the Circle class. But with the help of DOTNETARX, you can use three or two points to create a circle. The following example explains how to create a circle through three points:

  Circles circle=new Circles(pt1,pt2,pt3);

For detailed explanation, you can refer to the help document in the accessory.

The second purpose of the derived classes is to access the entity which is added into the database. We take two examples to explain this. First is not using the derived classes:

Circle circle=new Circle (center,normal,radius); 
//Because the circle is not added into database, 

//changing the circle�s radius is allowed 

circle.Radius=1;
//Add the circle into the database 

Tools.AddEntity(circle);
circle. Radius =2;
//Error,because the circle is added into the database,

//you must open it first, then operate on it

Codes using the derived classes:

Circles circle =new Circles (center, radius);//even the constructor is more simple

      circle. Radius =1;// Because the circle is not added into database, 

                        // changing the circle�s radius is allowed


Tools.AddEntity(circle);// Add the circle into the database 

// Though the circle is added into the database, you can edit its property

circle. Radius =2;