AutoCAD DevBlog

Turn on/off the running osnap

By Balaji Ramamoorthy

To turn on or off the running osnap, simply set the SNAPMODE system variable to 1 or 0.

Here is a sample code :

// Turn-off running osnap

Application.SetSystemVariable("SNAPMODE", 0);

 

// Turn-on running osnap

Application.SetSystemVariable("SNAPMODE", 1);

The various osnap options are governed by the value of the OSMODE system variable. Here is a post that describes setting of the OSMODE system variable. The values that the OSMODE system variable can take can be found in the AutoCAD documentation.

Prior to AutoCAD 2009, If object snap (Osnap) is turned off, AutoCAD adds 16384, to the current setting for the variable OSMODE. This allows applications to identify the current setting for OSMODE.

For instance, when you activate the "endpoint" object snap and Osnap is enabled, OSMODE contains 1 as its value. If object snap is disabled, OSMODE will contain 16385 as its value (1 + 16384).

Here is a sample code for this :

Int16 osmode = (Int16)Application.GetSystemVariable("OSMODE");

String msg = String.Empty;

if ((osmode & 16384) == 0)

{

    msg = String.Format

            (

                "OSnaps are Disabled. Value of OSMODE = {0}",

                osmode

            );

}

else

{

    msg = String.Format

            (

                "OSnaps are Enabled. Value of OSMODE = {0}",

                osmode

            );

}

Making a filtered selection set using Visual LISP (ActiveX functions)

By Balaji Ramamoorthy

The ActiveX method SelectionSet.Select to create a filtered set of database objects that meet this criteria:

Block references, such as INSERT entities, and that have extended entity data that is registered under application name "MYAPP"

The plain AutoLISP expression is: (ssget "X" '((0 . "INSERT") (-3 ("MYAPP"))))

Here is the code using the ActiveX call :

(defun c:myappSet ()

 

    (vl-load-com)

 

    (setq loAcad    (vlax-get-acad-object)

          loDoc        (vla-get-activedocument loAcad)

          loSelectionSet (vla-add (vla-get-selectionsets loDoc) "filtSet")

    )

 

    (setq filtArray (vlax-make-safearray vlax-vbInteger '(0 . 1))

          filtVar   (vlax-safearray-fill filtArray (list 0 1001))

          filtType  (vlax-make-variant

                        filtVar

                        (logior vlax-vbarray vlax-vbInteger)

                    )

    )

 

    (setq filtArray (vlax-make-safearray vlax-vbVariant '(0 . 1))

          filtVar   (vlax-safearray-fill filtArray (list "INSERT" "MYAPP"))

          filtData  (vlax-make-variant

                        filtVar

                        (logior vlax-vbarray vlax-vbVariant)

                    )

    )

 

    (vla-select

                loSelectionSet

                acSelectionSetAll

                nil

                nil

                filtType

                filtData

    )

 

    (setq count (vla-get-count loSelectionSet))

    (princ count)

 

    (setq ssets (vla-get-selectionsets loDoc))

    (vla-delete (vla-item ssets "filtSet"))

 

    (princ)

)

It is tempting for a Visual LISP developer to supply list arguments for the parameters filtType and filtData in the vla-select call, but ActiveX does not comprehend lists. The filtType parameter requires an array of integers while filtData is permitted to be a array of variant types.

For a closer examination of safearrays and variants, see the Visual LISP Developer's Guide. Refer to the section entitled "Converting AutoLISP Data Types to ActiveX Data Types".

Also, the group code designating xdata is 1001 instead of -3. This is different, of course, from the Visual LISP approach to filtering xdata, which makes use of the -3 extended data sentinel rather than group code.

Modifying AutoCAD support Path through .NET

By Virupaksha Aithal

You can use AutoCAD ActiveX API to manipulate the AutoCAD support path. Refer below code. As usual below code uses late binding technique while accessing ActiveX API.

[CommandMethod("AddSupportPath")]

static public void AddSupportPath()

{

 

    object acadObject = Application.AcadApplication;

 

    object preferences =

            acadObject.GetType().InvokeMember("Preferences",

            BindingFlags.GetProperty,

            null, acadObject, null);

 

    //get the files

    object files =

            preferences.GetType().InvokeMember("Files",

            BindingFlags.GetProperty,

            null, preferences, null);

 

    //get the support path SupportPath

    string supportPath =

            (string)files.GetType().InvokeMember("SupportPath",

            BindingFlags.GetProperty,

            null, files, null);

 

    Document doc = Application.DocumentManager.MdiActiveDocument;

    Editor ed = doc.Editor;

 

    if (!supportPath.Contains("C:\\BatchPublish"))

    {

        supportPath = supportPath + ";" + "C:\\BatchPublish";

 

        object[] dataArry = new object[1];

        dataArry[0] = supportPath;

        files.GetType().InvokeMember("SupportPath",

                         BindingFlags.SetProperty,

                         null, files, dataArry);

 

        ed.WriteMessage(supportPath + "\n");

    }

    else

    {

        ed.WriteMessage("Support path already present\n");

    }

 

}

Making sure new layout has a Viewport when created

By Virupaksha Aithal

An AutoCAD setting in the Options dialog controls behavior of adding a viewport to new layouts. You can turn off the creating viewports in newly created layouts. You can find the setting along this path:

'Options' dialog
    -> 'Display' tab
        -> 'Layout Elements' group
            -> 'Create Viewport in New Layouts' check box.

This can be controlled using AutoCAD ActiveX API too. It's ThisDrawing.Application.Preferences.Display.LayoutCreateViewport. The following code does the work exactly:

[CommandMethod("LayoutTest")]

public static void LayoutTest()

{

    Object acadObject = Application.AcadApplication;

 

 

    object preferences =

            acadObject.GetType().InvokeMember("Preferences",

            BindingFlags.GetProperty,

            null, acadObject, null);

 

    object display =

                preferences.GetType().InvokeMember("Display",

                BindingFlags.GetProperty,

                null, preferences, null);

 

    object layoutProperty =

                display.GetType().InvokeMember("LayoutCreateViewport",

                BindingFlags.GetProperty,

                null, display, null);

    //now set the value to true.

    if (Convert.ToBoolean(layoutProperty) == false)

    {

        object[] dataArry = new object[1];

        dataArry[0] = true;

        display.GetType().InvokeMember("LayoutCreateViewport",

                          BindingFlags.SetProperty,

                          null, display, dataArry);

    }

 

}

Converting C# to Java – An Experiment (Part 3)

By Stephen Preston

• In part 1 of this series I created a simple task list prioritization tool for AutoCAD written in C#. This was based on two classes: Item and PrioritizerCore.
• In part 2, I setup an Android app project in Eclipse, and migrated my Item class from C# to Java, discovering how very similar the two languages are.
• Today, I'll migrate the PrioritizerCore class. (As for the Item class, the goal today is to get the code to compile in Eclipse - we'll check the logic still works when we hook the classes into a working Android app).

We'd already copied the PrioritizerCore C# code into a PrioritizerCore.java file in our Android project, so we can just jump in and start editing. Before making additional changes, we'll go through the code and make the same edits as we did for Item without further comment:

• Change string to String and bool to boolean.
• Change LIst to ArrayList.
• Change the Serializable attibute to the Java Serializable interface.
• Change properties to get/set methods, and change calls to properties in the same way.
• Change all function names to start with a lowercase character instead of uppercase.
• USe intellisense to reference missing packages.

 That removes the vast majority of compilation errors. Those that remain are new.

The first new error we encounter is the foreach loop - which is really handy for iterating the elements of a collection. The C# code looks like this:

      foreach (Item i in m_ItemList)

Java has an equivalent, but the syntax is slightly different. We change that line to:

      for (Item i : m_ItemList)

which I really like - its even more succinct than the C# :-).

The next error is:

  public void sort()
  {
    m_ItemList.sort(new ItemComparer());
  }

Again Java has an equivalent of the sort method and the equivalent of a Comparator. We change our code to:

  public void sort()
  {
    Collections.sort(m_ItemList, new ItemComparer());
  }

As you'd expect, the next error is in our custom comparator definition. We change 

  private class ItemComparer : IComparer<Item>

to

  private class ItemComparer implements Comparator<Item>

 

And that's it. No more errors.PrioritizerCore.java now looks like this:

 

package Preston.Stephen.Prioritizer;

import java.io.Serializable;
import java.util.ArrayList;
import java.util.Collections;
import java.util.Comparator;


//PrioritizerCore  is responsible for handling the list of Items.
//[Serializable()]
public class PrioritizerCore implements Serializable
{

  private static final long serialVersionUID = 1L;
  private ArrayList<Item> m_ItemList;

  //Constructor
  public PrioritizerCore()
  {
    m_ItemList = new ArrayList<Item>();
  }

  //Adds a new Item to the list 
  // but only if the name (ItemText) is unique
  public boolean addItem(String strItemText)
  {
    Item tmpItem = new Item();
    tmpItem.setItemText(strItemText);
    if (m_ItemList.contains(tmpItem))
      return false;

    m_ItemList.add(tmpItem);
    return true;
  }


  //Returns Item at position 'index' in list.
  //Returns null if index is outside list bounds.
  public  Item getAtIndex(int index)
  {
    if (index >= 0 & index < m_ItemList.size())
    {
      return m_ItemList.get(index);
    }
    else
    {
      return null;
    }
  }

  //Clears the list
  public void reset()
  {
    m_ItemList.clear();
  }

  //Read-only property
  //Returns number of items in the list
  public  int getItemCount()
  {
    return m_ItemList.size();
  }


  //Returns true if any priorities have been set in list
  //(Which also means there must be at least two items in the list)
  public boolean hasPriorities()
  {
      for (Item i : m_ItemList)
      {
        if (i.getScore() > 0)
        {
          return true;
        }
      }
      return false;
  }


  //Sort list - highest priority Item first
  //If Priorities are equal, sort in ascending alphabetical order
  public void sort()
  {
    Collections.sort(m_ItemList, new ItemComparer());
  }

  //Sort in order of descending Score. 
  //If Result is same, sort on ascending Text.
  private class ItemComparer implements Comparator<Item>
  {
    public int compare(Item x, Item y)
    {
      //If items have same prioritization score, use prioritization
      // between the two items to sort. If that doesn't work, sort
      // alphanumerically on ItemText.
      if (x.getScore() == y.getScore())
      {

        if (x.IsBetterThan(y))
        {
          return -1;
        }
        else if (y.IsBetterThan(x))
        {
          return 1;
        }
        else
        {
          return x.getItemText().compareTo(y.getItemText());
        }
      }

      //If items have different priority scores, then sort on that.
      if (x.getScore() > y.getScore())
        return -1;
      //if (x.iResult < y.iResult) - the only option left
      return 1;
    }
  }
}

 

Here's a summary of the migration issues we found today:

• Java has a 'foreach' equivalent - for (Item i : m_ItemList).
• The Java 'sort' method is a static method of the Collection class instead of an instance method of a specific collection.
• The Java equivalent of the C# IComparer interface is IComparator (which I believe is more grammatically correct :-).

Next time we'll hook the PrioritizerCore and Item classes into a simple Android Activity, so we can display a list of Items in an Android ListView.

_______________________________

Credit where its due:

• I'm using Java2HTML (as advertised by Kean Walmsley) to copy the formatted code in Eclipse into my blog posts.
• This C# to Java comparison cheat sheet was very helpful when working out how to migrate my code.

Switching to a single viewport configuration

By Balaji Ramamoorthy

If there are multiple model-space viewports and to switch to a single model-space viewport configuration, you could use the -VPORTS command and specify the SI option.

For example :

acedCommand(RTSTR, L".-VPORTS", RTSTR, L"SI", RTNONE);

The other way to do this is to erase the viewport table records. When there are multiple model space viewports, you will find the same number of viewport table records in the viewport table. They all have the same name. To switch to a single viewport, all the viewports except one may be erased and the last remaining viewport can be set to cover the whole area.

Here is a sample code :

Acad::ErrorStatus es = acedVports2VportTableRecords();

AcDbDatabase* pDb

            = acdbHostApplicationServices()->workingDatabase();

 

AcDbViewportTable* pVportTable = NULL;

es = pDb->getViewportTable(pVportTable, AcDb::kForRead);

if(es == Acad::eOk)

{

    int vpCnt = 0;

    AcDbViewportTableIterator *pIter = NULL;

    es = pVportTable->newIterator(pIter);

    if(es == Acad::eOk)

    {

        for (;!pIter->done();pIter->step())

        {

            AcDbViewportTableRecord *pVTR = NULL;

            es = pIter->getRecord(pVTR, AcDb::kForRead);

            if(es == Acad::eOk)

            {

                const TCHAR* vtrname;

                if(pVTR->getName(vtrname) == Acad::eOk)

                {

                    if (_tcscmp(vtrname, ACRX_T("*Active"))==0)

                    {

                        vpCnt++;

                    }

                }

                pVTR->close();

            }

        }

        delete pIter;

    }

 

    for(int x = 0; x < vpCnt-1; x++)

    {

        AcDbViewportTableRecord *pVTR = NULL;

        es = pVportTable->getAt(

                                    ACRX_T("*Active"),

                                    pVTR,

                                    AcDb::kForWrite

                                );

        if(es == Acad::eOk)

        {

            pVTR->erase(true);

            pVTR->close();

        }

    }

 

    // Set the last viewport to cover the full area

    AcDbViewportTableRecord *pVTR = NULL;

    es = pVportTable->getAt(

                                ACRX_T("*Active"),

                                pVTR,

                                AcDb::kForWrite

                            );

    if(es == Acad::eOk)

    {

        AcGePoint2d ll, ur;

        ll.set(0,0);

        ur.set(1,1);

        pVTR->setCenterPoint(AcGePoint2d(0, 0));

        pVTR->setHeight(100);

        pVTR->setWidth(100);

        pVTR->setViewDirection(AcDb::kTopView);

        pVTR->setLowerLeftCorner(ll);

        pVTR->setUpperRightCorner(ur);

        pVTR->close();

    }

    pVportTable->close();

}

es = acedVportTableRecords2Vports();

Preventing a block from being purged

By Balaji Ramamoorthy

We will look at two approaches to prevent a block from getting purged.

1) Create a block reference out of the block and assign it to a hidden layer

2) Create a custom object that stores a hard pointer to the block. An instance of the custom object can be stored within your dictionary stored under the named object dictionary.

Here is the code snippet for the first method :

static Acad::ErrorStatus CreateBlock_Method1()

{

    Acad::ErrorStatus es;

    AcDbBlockTable *pBlockTable = NULL;

 

    AcDbDatabase *pDb

            = acdbHostApplicationServices()->workingDatabase();

 

    pDb->getBlockTable(pBlockTable, AcDb::kForWrite);

    AcDbBlockTableRecord* pAnonBlock = new AcDbBlockTableRecord();

    pAnonBlock->setName(_T("*U"));

 

    AcDbObjectId idAnonBlock = AcDbObjectId::kNull;

    pBlockTable->add(idAnonBlock, pAnonBlock);

 

    AcDbCircle *pCircle = new AcDbCircle(

                                            AcGePoint3d::kOrigin,

                                            AcGeVector3d::kZAxis,

                                            5.0

                                        );

 

    pAnonBlock->appendAcDbEntity(pCircle);

 

    pCircle->close();

 

    pAnonBlock->close();

 

    // Method : 1

    // Create an anonymous layer and use it for the

    // newly created block reference.

    AcDbObjectId layerId = AcDbObjectId::kNull;

    AcDbLayerTable* lTable;

    es = pDb->getSymbolTable(lTable, AcDb::kForWrite);

 

    if(Acad::eOk == es && lTable)

    {

        AcDbLayerTableRecord* lTblRec = new AcDbLayerTableRecord;

        lTblRec->setName(ACRX_T("TEST"));

        lTblRec->setIsHidden(true);

        AcCmColor layerColor;

        layerColor.setColorIndex(2);

        lTblRec->setColor(layerColor);

 

        if (lTable->add(layerId, lTblRec) != Acad::eOk)

            AfxMessageBox(_T("ERROR Creating Layer"));

        else

            lTblRec->close();

 

        lTable->close();

    }

 

    // Create a block reference and set to the hidden layer

    AcDbBlockReference *pBlkRef

            = new AcDbBlockReference(

                                        AcGePoint3d::kOrigin,

                                        idAnonBlock

                                    );

    pBlkRef->setLayer(layerId, true, true);

 

    AcDbBlockTableRecord *pModelSpace;

    pBlockTable->getAt(

                        ACDB_MODEL_SPACE,

                        pModelSpace,

                        AcDb::kForWrite

                      );

 

    pModelSpace->appendAcDbEntity(pBlkRef);

 

    pBlkRef->close();

    pModelSpace->close();

    pBlockTable->close();

 

    return Acad::eOk;

}

Here is the code snippet for the second method :

// Step : 1

// Create a basic custom object using the ARX wizard

 

 

// Step : 2

// In your custom object header file, add an id that will

// hold the ObjectId of the block that we are trying to

// prevent getting purged.

public:

    // Id of the object to prevent purge

    AcDbObjectId _Id;

 

 

// Step : 3

// Ensure that the objectId of the block is filed.

// For this make the following changes to the

// dwgInFields and dwgOutFields methods.

Acad::ErrorStatus AdsMyCustomObj::dwgOutFields

                                    (AcDbDwgFiler *pFiler) const

{

    // ...

    //----- Output params

    pFiler->writeHardPointerId(_Id);

 

    return (pFiler->filerStatus ()) ;

}

 

Acad::ErrorStatus AdsMyCustomObj::dwgInFields

                                        (AcDbDwgFiler *pFiler)

{

    // ...

    //----- Read params

    AcDbHardPointerId hardPointerId;

    pFiler->readHardPointerId(&hardPointerId);

    _Id = hardPointerId;

 

    return (pFiler->filerStatus ()) ;

}

 

 

// Step : 4

// Here is the method that creates a block table record

// and stores its id in the custom object instance.

// The custom object instance is stored in a custom dictionary

// under the named object dictionary.

static Acad::ErrorStatus CreateBlock_Method2( )

{

    Acad::ErrorStatus es;

    AcDbBlockTable *pBlockTable = NULL;

 

    AcDbDatabase *pDb

            = acdbHostApplicationServices()->workingDatabase();

 

    pDb->getBlockTable(pBlockTable, AcDb::kForWrite);

    AcDbBlockTableRecord* pAnonBlock = new AcDbBlockTableRecord();

    pAnonBlock->setName(_T("*U"));

 

    AcDbObjectId idAnonBlock = AcDbObjectId::kNull;

    pBlockTable->add(idAnonBlock, pAnonBlock);

 

    AcDbCircle *pCircle = new AcDbCircle(

                                            AcGePoint3d::kOrigin,

                                            AcGeVector3d::kZAxis,

                                            5.0

                                        );

 

    pAnonBlock->appendAcDbEntity(pCircle);

    pCircle->close();

    pAnonBlock->close();

 

    // Method : 2

    // Custom object in the NOD to store the hard pointer

    // to the block

    AcDbObjectPointer<AcDbDictionary> pNOD(

                                            pDb->namedObjectsDictionaryId(),

                                            AcDb::kForWrite

                                          );

    AcDbDictionary *pMyDict = NULL;

 

    AcDbObject *pMyDictObject = NULL;

    if(pNOD->getAt(

                    ACRX_T("MYOBJDICT"),

                    pMyDictObject,

                    AcDb::kForWrite

                  ) == Acad::eOk)

    {

        pMyDict = AcDbDictionary::cast(pMyDictObject);

    }

    else

    {

        pMyDict = new AcDbDictionary();

        AcDbObjectId DictObjectId = AcDbObjectId::kNull;

        pNOD->setAt(ACRX_T("MYOBJDICT"), pMyDict, DictObjectId);

    }

 

    AcDbObjectId customObjectId;

    AdsMyCustomObj *pCustObj = new AdsMyCustomObj();

    pCustObj->_Id = idAnonBlock;

    pMyDict->setAt (_T("DETAILS"), pCustObj, customObjectId);

    pCustObj->close ();

 

    pMyDict->close();

    pNOD->close();

 

    pBlockTable->close();

    return Acad::eOk;

}

Creating a anonymous Layer

By Virupaksha Aithal

To create anonymous Layer, you need to call “AcDbLayerTable::setIsHidden()” API as shown in below code. Anonymous layers are not shown in layer manager and hence users can not edit/delete the setting of anonymous layers.

void CreateAnonymousLayer()

{

    AcDbObjectId layerId = AcDbObjectId::kNull;

    AcDbLayerTable* lTable = NULL;

 

    AcDbDatabase *pDb = acdbHostApplicationServices()->

                                        workingDatabase();

 

    Acad::ErrorStatus es =

                pDb->getSymbolTable(lTable, AcDb::kForWrite);

 

    if(Acad::eOk == es && lTable)

    {

          AcDbLayerTableRecord* lTblRec =

                new AcDbLayerTableRecord();

          lTblRec->setName(ACRX_T("TEST"));

 

          lTblRec->setIsHidden(true);

 

          if (lTable->add(layerId, lTblRec) != Acad::eOk)

              ::acutPrintf(_T("ERROR Creating Layer\n"));

          else

            lTblRec->close();

 

          lTable->close();

    }

 

}

.NET

 

[CommandMethod("Hiddenlayer")]

public void Hiddenlayer()

{

 Document doc = Application.DocumentManager.MdiActiveDocument;

 Database db = doc.Database;

 Editor ed = doc.Editor;

 

 using (Transaction tr =

        db.TransactionManager.StartTransaction())

 {

     LayerTable table =

     tr.GetObject(db.LayerTableId, OpenMode.ForWrite) as LayerTable;

 

     LayerTableRecord Anonymous = new LayerTableRecord();

     Anonymous.Name = "Test";

     Anonymous.IsHidden = true;

 

 

     table.Add(Anonymous);

     tr.AddNewlyCreatedDBObject(Anonymous, true);

     tr.Commit();

 

 }

}

Converting a Polyline2d to Polyline

By Virupaksha Aithal

For converting Polyline2d to Polyline, you can use Polyline.ConvertFrom API. But this API throws the eInvalidContext exception when the second argument for ConvertFrom() is set to true, inside the transaction. The true argument will handover the same object Id's to the new entity. This is fine except for a rule that AcDbObject::handOverTo() (defined in ObjectARX) cannot be used inside of a transaction. So, to solve issue, use Open and Close technology as shown in below code.

[CommandMethod("TestConvertPoly")]

public void testConvertPoly()

{

 Document doc = Application.DocumentManager.MdiActiveDocument;

 Database db = doc.Database;

 Editor ed = doc.Editor;

 

 // select the entity

 PromptEntityResult res = ed.GetEntity("Select PolyLine: ");

 // if ok

 if (res.Status == PromptStatus.OK)

 {

     // use the using keyword so that the objects auto-dispose

     //(close)  at the end of the brace

     // open for write otherwise ConvertFrom will fail

     using (Entity ent =

         (Entity)res.ObjectId.Open(OpenMode.ForRead))

     {

 

         // if it's a polyline2d

         if (ent is Polyline2d)

         {

             Polyline2d poly2d = (Polyline2d)ent;

             poly2d.UpgradeOpen();

 

             // again use the using keyword to ensure auto-closing

             using (Autodesk.AutoCAD.DatabaseServices.Polyline poly

                 = new Autodesk.AutoCAD.DatabaseServices.Polyline())

             {

                 poly.ConvertFrom(poly2d, true);

             }

         }

     }

 }

}

How to use AcDbRegion::getAreaProp()

By Xiaodong Liang

The first three parameters for the function are described as

- origin Returns origin of the region
- xAxis Returns xAxis of the region
- yAxis Returns yAxis of the region

But considering the const declaration for these parameters
virtual Acad::ErrorStatus getAreaProp(
                           const AcGePoint3d& origin,
                           const AcGeVector3d& xAxis,
                           const AcGeVector3d& yAxis, ... );

It's clear that these three parameters are not output parameters but input parameters. Using parameters that were not initialized properly results in the function returning Acad::eInvalidInput.

Here is a correct application of AcDbRegion::getAreaProp():

// note for code brevity, some error checking are omitted

//

void getRegionAreaProp()

{

    ads_name eNam;

    ads_point pt;

    AcDbObjectId eId;

 

    if (acedEntSel(L"\nSelect an region: ", eNam, pt) != RTNORM)

    {

        acutPrintf(L"\nNothing selected.");

        return;

    }

    acdbGetObjectId(eId, eNam);

 

    AcDbEntity* pEnt = NULL;

    if(acdbOpenAcDbEntity(pEnt, eId, AcDb::kForRead) != Acad::eOk)

    {

        acutPrintf(L"\nError open entity.");

        return;

    }

    AcDbRegion* pReg = AcDbRegion::cast(pEnt);

    if(!pReg)

    {

        pEnt->close();

        return;

    }   

    double perimeter, area, momInertia[2],

           prodInertia, prinMoments[2],   

           radiiGyration[2];

    AcGePoint2d centroid, extentsLow, extentsHigh;

    AcGeVector2d prinAxes[2];

 

    AcGePoint3d origin;

    AcGeVector3d xAxis;

    AcGeVector3d yAxis;

 

    // initialize the three arguments

    AcGePlane plane;

    pReg->getPlane(plane);

    plane.getCoordSystem(origin, xAxis, yAxis);

 

    Acad::ErrorStatus es = pReg->getAreaProp(

        // these (3) are the input parameters

        origin, xAxis, yAxis,

        perimeter,

        area,

        centroid,

        momInertia,

        prodInertia,

        prinMoments,

        prinAxes,

        radiiGyration,

        extentsLow,

        extentsHigh);

 

    assert(es == Acad::eOk);

    // you can determine what to do exactly with the results

    // here I just print a message

    acutPrintf(L"\nSucceded in getting an region's area prop.");

    pReg->close();

}