AutoCAD DevBlog

Polysamp/ComPolygon help file does not work

By Adam Nagy

I was looking at the ARX 2011 SDK\samples\entity\polysamp project and I can see that under the compoly subfolder there is a WinHelp project (compoly.hpj, compoly.hm, compoly.rtf). Using Microsoft Help Workshop we can create a WinHelp file (*.hlp) from that, which is referenced from compoly.idl, and that should provide some help somewhere. However when I run the sample, create a ComPolygon entity, select it and press F1, then it still takes me to the AutoCAD help instead of the help provided with polysamp.

Solution

The help file provided with polysamp is only for its COM interface.

Once you created the *.hlp file and placed it where it can be found (e.g. with the dbx files), then when you are inside a programming environment like VBA for AutoCAD (VBAIDE) and select one of the ComPolygon specific properties/methods and click F1 then the appropriate topic inside that help file will come up:

This help file does not provide help in other contexts, inc. when inside the AutoCAD drawing environment and you select an AsdkPoly entity, whose COM wrapper is ComPolygon, and click F1.

Add Ribbon tab to Contextual Tab Selector Rule using CUI API

By Adam Nagy

I'd like to programmatically add my Ribbon tab to the Contextual Tab Selector rule that I created. How could I do it?

Solution

Here is a sample code that shows how to do it using the CUI API. In this case we'll add the Annotation Ribbon tab to the AcArcSelected rule which is part of the AcContextualTabSelectorRules.xaml file.

Once you run the below command, whenever you select an arc in the drawing the Annotation tab will show up.

using System;

using Autodesk.AutoCAD.Runtime;

using Autodesk.AutoCAD.Customization;

using acApp = Autodesk.AutoCAD.ApplicationServices.Application;

using System.Collections.Generic;

 

[assembly: CommandClass(typeof(ContextualTab.AEN1Commands))]

 

namespace ContextualTab

{

  public class AEN1Commands

  {

    [CommandMethod("MyCommand")]

    static public void Cmd1()

    {

      // Part of AcContextualTabSelectorRules.xaml

      const string kRuleId = "AcArcSelected";

 

      // Id of Annotation tab

      const string kTabId = "ID_TabAnnotate";

 

      // Get customization section

 

      string menuName = (string)acApp.GetSystemVariable("MENUNAME");

      CustomizationSection cs =

        new CustomizationSection(menuName + ".cuix");

 

      // Check if the rule is already used

 

      RibbonRoot rr = cs.MenuGroup.RibbonRoot;

      RibbonTabSelector ts = null;

 

      foreach (RibbonTabSelector tsIter in rr.RibbonTabSelectors)

        if (tsIter.Rule == kRuleId)

        {

          ts = tsIter;

          break;

        }

 

      // If it's not used then create it

 

      if (ts == null)

      {

        ts = (RibbonTabSelector)System.Activator.CreateInstance(

               typeof(RibbonTabSelector), true

             );

 

        ts.Rule = kRuleId;

        rr.RibbonTabSelectors.Add(ts);

      }

 

      // Add the tab we want to make appear

 

      if (!new List<string>(ts.Tabs).Contains(kTabId))

        ts.Append(kTabId);

 

      // Save modifications and reload

 

      if (cs.IsModified)

      {

        cs.Save();

 

        acApp.ReloadAllMenus();

      }

    }

  }

}

Show LAYER dialog synchronously

By Adam Nagy

I would like to run the LAYER command from my own command. Unfortunately, it seems that the LAYER dialog only shows once my command is finised. Would it be possible to show this dialog during my command and then continue with my command once the dialog is closed?

Solution

First of all, for a few releases now the layer dialog has been modeless. However, it has a setting that enables the old behaviour: LAYERDLGMODE

Also, to start another command synchronously, you would need to P/Invoke acedCmd() from your .NET project.

Since you try to run the LAYER command from inside your command, it starts in command line mode. If you want to force it to show the dialog, then you also need to P/Invoke acedInitDialog(). This has mangled name, which also means that it may be different depending on the OS type (32 bit vs. 64 bit) and the version of AutoCAD, so make sure that you are using the correct mangled name of the function.

You can use dumpbin.exe or depends.exe to get this information from acad.exe. You can find further information about these utilities on the internet.

Here is the .NET project that does what you need in case of AutoCAD 2011 on 32 bit OS:

using System;

using System.Runtime.InteropServices;

 

using Autodesk.AutoCAD.Runtime;

using Autodesk.AutoCAD.ApplicationServices;

using acApp = Autodesk.AutoCAD.ApplicationServices.Application;

using Autodesk.AutoCAD.DatabaseServices;

 

namespace StartCommand

{

  public class Command

  {

    [DllImport(

      "acad.exe",

      CallingConvention = CallingConvention.Cdecl,

      CharSet = CharSet.Unicode,

      EntryPoint = "acedCmd")]

    public static extern int acedCmd(System.IntPtr resBuf);

 

    // Mangled entry point may be different in case of

    // different OS (32 bit vs 64 bit) and different AutoCAD versions

 

    [DllImport(

      "acad.exe",

      CallingConvention = CallingConvention.Cdecl,

      CharSet = CharSet.Unicode,

      EntryPoint = "[email protected]@[email protected]")]

    public static extern bool acedInitDialog(bool useDialog);

 

    [CommandMethod("StartCommand1")]

    public void StartCommand1()

    {

      // Do something

      // ...

 

      acApp.DocumentManager.MdiActiveDocument.Editor.WriteMessage(

        "\nCommand Started ...\n"

      );

 

      // Now show the LAYER dialog

      // First make sure that we use the modal version

 

      short dlgMode = (short)acApp.GetSystemVariable("LAYERDLGMODE");

      acApp.SetSystemVariable("LAYERDLGMODE", 0);

 

      // Execute the LAYER command

 

      using (ResultBuffer rb = new ResultBuffer())

      {

        rb.Add(new TypedValue((int)LispDataType.Text, "_LAYER"));

 

        // Make sure that not the command line version gets started

 

        acedInitDialog(true);

 

        acedCmd(rb.UnmanagedObject);

      }

 

      // Restore the value

 

      acApp.SetSystemVariable("LAYERDLGMODE", dlgMode);

 

      // Continue with our command

 

      acApp.DocumentManager.MdiActiveDocument.Editor.WriteMessage(

        "\nCommand Continued ...\n"

      );

    }

  }

}

AcDbSymbolUtilities

By Virupaksha Aithal

The class AcDbSymbolUtilities::Services (typedef AcDbSymUtilServices) provides utility functions that are accessed by calling acdbSymUtil(). This utility has functions related to various symbol table operation like getting the model space id, paper space id, layer zero id etc.

Below code shows the procedure to get the model space id directly.

Refer blog http://adndevblog.typepad.com/autocad/2012/04/did-you-know-about-this-utility-class.html for .NET Equivalent

void getModelspaceId()

{

    AcDbDatabase *pDb =

      acdbHostApplicationServices()->workingDatabase();

 

    //get model psace id

    AcDbObjectId modelId;

    modelId = acdbSymUtil()->blockModelSpaceId(pDb);

 

    //get layer zero id.

    AcDbObjectId LayerId;

    LayerId = acdbSymUtil()->layerZeroId(pDb);

 

    //other functions...

}

 

AcDbDictUtil utility class

By Virupaksha Aithal

AcDbDictUtil utility class functions are very handy for quick one-time access to the name or ID of a dictionary entry. Below sample shows the procedure to use AcDbDictUtil to get the layout id given its name. Similar there are function to get group, material, plotstyle etc.

void getLayout()

{

    ACHAR nameBuf[150];

    if (acedGetString(Adesk::kTrue,

        _T("\nEnter layout name to get: "), nameBuf) != RTNORM)

               return;

 

    AcDbDatabase *pDb =

      acdbHostApplicationServices()->workingDatabase();

 

    AcDbObjectId Id;

    Acad::ErrorStatus es = AcDbDictUtil::getLayoutId(Id, nameBuf,

                                                                pDb);

 

    if(es == Acad::eOk)

    {

        acutPrintf(_T("Layout %s found \n"), nameBuf);

    }

    else

    {

        acutPrintf(_T("Unabale to find layout with name %s\n"),

                        nameBuf);

    }

 

}

The Right Tools for the Job – AutoCAD Part 4

by Fenton Webb

Leading on from Part 3 I wanted to talk to you about the importance of ObjectARX compiler settings.

As I mentioned before, the code I used to test the performance of the various languages was all written a while ago and that I had decided to port them to AutoCAD 2011 in order to rerun the tests.

When I ported the Visual Studio 2005 ObjectARX and .NET projects to Visual Studio 2008 I simply recompiled in Release mode and started testing.

What I found very strange was that the Release mode .NET tests were running about 35% *faster* than the Release mode ObjectARX tests?!?!? Obviously, this could never be the case because .NET wraps ObjectARX so ObjectARX will always be faster that .NET in the AutoCAD world.

I found that the problem was that the Release mode ObjectARX Compiler Optimization settings were way off, probably due to some Visual Studio project migration issue or maybe even a bug in the old ObjectARX wizard that created the project settings. Once I updated the settings, everything started to work as expected, as you can see in the results that I posted previously.

At this point, I decided to take some time to try and see which settings affected the performance best.

What I found was that, for my test harness code, the Visual Studio Project Property page settings “Optimization=Max Speed” and “Favor Size or Speed=Favor Fast Code” settings displayed in Red below in made the greatest *difference* in performance time, without those set correctly .NET ran faster! Also, you should set the other settings as you can see below - Let’s call is Stage 1 - It got me to around 8.51 seconds for 1,000,000 Xrecords, taken as an average from 3 different test runs…

Notice that I’m not using “Whole Program Optimization” yet. With that setting turned on (and also inside of the Linker Optimization page “Link Time Code Generation” (see just below)),  let’s call this Stage 2, the time went down again to 8.047 seconds, taken as an average from 3 different test runs…

You could be confused by this given that my test harness code is in one .cpp file, but remember that we are linking many ObjectARX modules, so that’s where the optimization comes in.

Next, setting “Enable String pooling=Yes” and “Buffer Security Check=No” surprisingly slowed things down to 8.96. I say surprisingly because I considered that my loop contained items which I figured turning off the Buffer Security Check switch would affect, must be the String pooling that is affecting it…

Changing back “Enable String pooling=No” and keeping “Buffer Security Check=No” did make things run slightly quicker with a time of 8.54, but still not quicker than its default setting, I find this strange…

So it seems that Stage 2 is the best settings for performance on AutoCAD 2011 with Visual Studio 2008, running my specific test harness.

Now to talk a little bit. I’m sure a lot of you out there have read the results of the settings and have not been too surprised about the results, am I right? But how many of your ObjectARX programmers have assumed that the your ObjectARX Release mode settings are optimal as I speak? Do you take time with every release to examine what new settings are and consider what each one might do (or not do) for your application? Did you double check the settings that the Visual Studio Project migration wizard created for you? I know that I don’t

So here’s some basic advice for all you ObjectARX programmers with regards AutoCAD ObjectARX Visual Studio Release mode project settings…

1. Never assume you have the best Visual Studio Release mode performance settings for your ObjectARX application.
2. Never trust the migration wizards, always check what they have done.
   1. Visual Studio is always being enhanced, make sure your migrated project has all of the latest, relevant project settings setup – especially for Release mode.
3. We take a lot of time creating the best Visual Studio project settings for your ObjectARX applications, you should check the ObjectARX samples to see what performance settings you should use.

Next I’m going to look at .NET performance and reveal some performance coding techniques that I use. See Part 5 here

VBA: How to setup selectionset filters for a block or layer?

By Philippe Leefsma

Q:

How do I use a selection set filter to select a block with a particular name
that is on a particular layer ?

A:

The following sample code allows you to select blocks based on this criteria:

1. selectALayer() - create a selectionset with entities on "layer1"
2. selectABlock() - create a selectionset with a block insert "testBlock"
3. selectABlockOnALayer() - create a selectionset with a block insert "testBlock" on "layer1"

Sub selectALayer()

   Dim sset As AcadSelectionSet
   Set sset = ThisDrawing.SelectionSets.Add("TestSet1")
  
   Dim filterType As Variant
   Dim filterData As Variant
   Dim p1(0 To 2) As Double
   Dim p2(0 To 2) As Double
  
   Dim grpCode(0) As Integer
   grpCode(0) = 8
   filterType = grpCode
   Dim grpValue(0) As Variant
   grpValue(0) = "Layer1"
   filterData = grpValue
   
   sset.Select acSelectionSetAll, p1, p2, filterType, filterData
  
   Debug.Print "Entities: " & str(sset.count)
  
   sset.Delete
  
End Sub

Sub selectABlock()

   Dim sset As AcadSelectionSet
   Set sset = ThisDrawing.SelectionSets.Add("TestSet2")
  
   Dim filterType As Variant
   Dim filterData As Variant
   Dim p1(0 To 2) As Double
   Dim p2(0 To 2) As Double
  
   Dim grpCode(0) As Integer
   grpCode(0) = 2
   filterType = grpCode
   Dim grpValue(0) As Variant
   grpValue(0) = "testBlock"
   filterData = grpValue
   
   sset.Select acSelectionSetAll, p1, p2, filterType, filterData
  
   Debug.Print "Entities: " & str(sset.count)
  
   sset.Delete
  
End Sub

Sub selectABlockOnALayer()

   Dim sset As AcadSelectionSet
   Set sset = ThisDrawing.SelectionSets.Add("TestSet3")
  
   Dim filterType As Variant
   Dim filterData As Variant
   Dim p1(0 To 2) As Double
   Dim p2(0 To 2) As Double
  
   Dim grpCode(0 To 1) As Integer
   grpCode(0) = 8
   grpCode(1) = 2
   filterType = grpCode
  
   Dim grpValue(0 To 1) As Variant
   grpValue(0) = "layer1"
   grpValue(1) = "testBlock"
   filterData = grpValue
  
   sset.Select acSelectionSetAll, p1, p2, filterType, filterData
  
   Debug.Print "Entities: " & str(sset.count)
  
   sset.Delete
  
End Sub

 

Converting an AcDbAlignedDimension into a vertical and horizontal AcDbRotatedDimension

By Philippe Leefsma

Q:

How can I convert an existing AcDbAlignedDimension into two AcDbRotatedDimensions, so one is vertical and the second horizontal?

A:

Following arx code addresses this question: to test it just run the "ConvertAlignedDim" method in a command and select an aligned dimension.

Acad::ErrorStatus postToDatabase (AcDbEntity *pEnt)

{

 AcDbObjectId idObj;

 Acad::ErrorStatus es;

 AcDbBlockTable *pBlockTable;

 AcDbBlockTableRecord *pSpaceRecord;

 

 if ( (es = acdbHostApplicationServices()->workingDatabase()->getBlockTable (pBlockTable, AcDb::kForRead)) == Acad::eOk )

 {

  if ( (es = pBlockTable->getAt (ACDB_MODEL_SPACE, pSpaceRecord, AcDb::kForWrite)) == Acad::eOk )

  {

   es = pSpaceRecord->appendAcDbEntity (idObj, pEnt);

   pSpaceRecord->close ();

  }

  pBlockTable->close ();

 }

 

 return es;

}

 

void CreateLinDim(const AcGePoint3d& pnt1, const AcGePoint3d& pnt2)

{

 //Create Horizontal dimension

 AcDbRotatedDimension *dimH = new AcDbRotatedDimension(0.0, pnt1, pnt2, pnt1 - AcGeVector3d  (0, 10, 0));

 postToDatabase (dimH);

 dimH->close();

 

 //Create Vertical dimension

 AcDbRotatedDimension *dimV = new AcDbRotatedDimension((4*atan(1.0))/2.0, pnt1, pnt2, pnt1 - AcGeVector3d (10, 0, 0));

 postToDatabase (dimV);

 dimV->close();

}

 

void ConvertAlignedDim(void)

{

 ads_name ename; 

 ads_point pickpt;

 

 int rc = acedEntSel(L"\nSelect aligned dimension: ", ename, pickpt);

 

 if(rc != RTNORM)

 {

  if (rc != RTCAN) acutPrintf(L"\nError selecting entity ");

  return;

 }

 

 AcDbObjectId dimId;

 acdbGetObjectId(dimId, ename);

 

 AcDbObject *pObj;

 acdbOpenObject(pObj, dimId, AcDb::kForWrite);

 AcDbAlignedDimension* pAlignDim = AcDbAlignedDimension::cast(pObj);

 

 if(!pAlignDim)

 {

  acutPrintf(L"\nEntity selected is not an aligned dimension...");

  pObj->close();

  return;

 }

 

 CreateLinDim(pAlignDim->xLine1Point(), pAlignDim->xLine2Point());

 

 //Get rid of original aligned dimension

 pAlignDim->erase();

 pAlignDim->close();

 

 return;

}

 

 

 

How to create multiple model space viewports from API?

By Philippe Leefsma

Q:

I would like to create multiple viewports in model space, for example four viewports that would divide equally the screen, like four different views of the same model. In addition I would like to do it automatically for each drawing that I create from the UI. How could this be achieved from arx?

A:

The code sample below illustrates how to create four viewports in model space, with possible different views of the model. For sake of simplicity, only the view parameters of the first viewport are set.

Concerning doing this processing on each new drawing, using the "AcApDocManagerReactor::documentCreated" event to place our viewport code can do the job.

void CreateViewPorts(AcDbDatabase* pDatabase, const ACHAR* vpName)

{

 AcDbViewportTable *pVT;

 pDatabase->getSymbolTable(pVT, AcDb::kForWrite);

 

 AcDbDictionary* pVisualStyleDic;

 pDatabase->getVisualStyleDictionary(pVisualStyleDic, AcDb::kForRead);

 

 AcGePoint2d ll, ur;

 AcDbObjectId vStyleId;

 

 AcDbViewportTableRecord* pVTR1=new AcDbViewportTableRecord;

 ll.set(0,0);

 ur.set(0.5,0.5);

 

 pVisualStyleDic->getAt(L"2dWireframe", vStyleId);

 

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

 pVTR1->setHeight(100);

 pVTR1->setWidth(100);

 pVTR1->setVisualStyle(vStyleId);

 pVTR1->setViewDirection(AcDb::kTopView);

 pVTR1->setLowerLeftCorner(ll);

 pVTR1->setUpperRightCorner(ur);

 pVTR1->setName(vpName);

 

 AcDbViewportTableRecord *pVTR2=new AcDbViewportTableRecord;

 ll.set(0,0.5);

 ur.set(0.5,1);

 pVTR2->setLowerLeftCorner(ll);

 pVTR2->setUpperRightCorner(ur);

 pVTR2->setName(vpName);

 

 AcDbViewportTableRecord *pVTR3=new AcDbViewportTableRecord;

 ll.set(0.5,0);

 ur.set(1,0.5);

 pVTR3->setLowerLeftCorner(ll);

 pVTR3->setUpperRightCorner(ur);

 pVTR3->setName(vpName);

 

 AcDbViewportTableRecord *pVTR4=new AcDbViewportTableRecord;

 ll.set(0.5,0.5);

 ur.set(1,1);

 pVTR4->setLowerLeftCorner(ll);

 pVTR4->setUpperRightCorner(ur);

 pVTR4->setName(vpName);

 

 

 pVT->add(pVTR1);

 pVT->add(pVTR2);

 pVT->add(pVTR3);

 pVT->add(pVTR4);

 

 pVT->close();

 

 pVTR1->close();

 pVTR2->close();

 pVTR3->close();

 pVTR4->close();

 

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

}

 

Accessing sub-entities using AssocPersSubentityIdPE in ARX or .Net

By Philippe Leefsma

Q:

How do I access the sub-entities of an AutoCAD entity in ObjectARX or .Net?

A:

Below are two samples in C++ and C# that illustrate how to access the AssocPersSubentityIdPE and use it to iterate through the vertices and edges of the selected entity.

////////////////////////////////////////////////////////////////////////////////////

//Use: Retrieves entity vertices & edges using AssocPersSubentityIdPE

//

////////////////////////////////////////////////////////////////////////////////////

void ArxSubEntityPE()

{

        Acad::ErrorStatus err;

 

        ads_name name;

        ads_point pt;

 

        if(acedEntSel(L"\nSelect an Entity: ", name, pt) != RTNORM)

                return;

 

        AcDbObjectId id;

        acdbGetObjectId(id, name);

 

        AcDbObjectPointer <AcDbEntity> pEntity(id, AcDb::kForRead);

 

        // Get the Protocol extension associated with the entity

        AcDbAssocPersSubentIdPE* const pAssocPersSubentIdPE =

                AcDbAssocPersSubentIdPE::cast(

                        pEntity->queryX(AcDbAssocPersSubentIdPE::desc()));

 

        if( pAssocPersSubentIdPE == NULL)

                return;

 

        AcArray <AcDbSubentId> vertexIds;

        pAssocPersSubentIdPE->getAllSubentities(

                pEntity,

                AcDb::kVertexSubentType,

                vertexIds);

 

        acutPrintf(L"\n- Vertex Subentities: ");

 

        for (int i = 0; i<vertexIds.length(); ++i)

        {

                AcDbFullSubentPath path(id, vertexIds[i]);

 

                AcDbPoint* pPoint = AcDbPoint::cast(pEntity->subentPtr(path));

       

                if (pPoint != NULL)

                {

                   AcGePoint3d pos = pPoint->position();

                   acutPrintf(L"\n . Vertex: [%.2f, %.2f, %.2f]",

                       pos.x, pos.y, pos.z);

                        delete pPoint;

                }

        }

 

        AcArray <AcDbSubentId> edgeIds;

        pAssocPersSubentIdPE->getAllSubentities(

                pEntity,

                AcDb::kEdgeSubentType,

                edgeIds);

       

        acutPrintf(L"\n- Edge Subentities: ");

 

        for (int i = 0; i<edgeIds.length(); ++i)

        {

                AcDbFullSubentPath path(id, edgeIds[i]);

 

                AcDbEntity* pSubEntity = pEntity->subentPtr(path);

       

                if (pSubEntity != NULL)

                {

                        acutPrintf(L"\n . %s (Id = %d)",

                                pSubEntity->isA()->name(),

                                edgeIds[i].index());

 

                        delete pSubEntity;

                }

        }

}

 

 

 

////////////////////////////////////////////////////////////////////////////////

//Use: Retrieves entity vertices, edges, faces using AssocPersSubentityIdPE

//

////////////////////////////////////////////////////////////////////////////////

[CommandMethod("SubEntityPE")]

public void SubEntityPE()

{

    Document doc = Application.DocumentManager.MdiActiveDocument;

    Database db = doc.Database;

    Editor ed = doc.Editor;

 

    PromptEntityOptions peo = new PromptEntityOptions(

        "\nSelect an Entity: ");

 

    PromptEntityResult per = ed.GetEntity(peo);

 

    if (per.Status != PromptStatus.OK)

        return; 

 

    using (Transaction Tx = db.TransactionManager.StartTransaction())

    {

        Entity entity = Tx.GetObject(per.ObjectId, OpenMode.ForRead)

            as Entity;

 

        ObjectId[] entId = new ObjectId[] { entity.ObjectId };

 

        IntPtr pSubentityIdPE = entity.QueryX(

            AssocPersSubentityIdPE.GetClass(

            typeof(AssocPersSubentityIdPE)));

 

        if (pSubentityIdPE == IntPtr.Zero)

            //Entity doesn't support the subentityPE

            return;

 

        AssocPersSubentityIdPE subentityIdPE =

            AssocPersSubentityIdPE.Create(pSubentityIdPE, false)

                as AssocPersSubentityIdPE;

 

        SubentityId[] vertexIds = subentityIdPE.GetAllSubentities(

            entity,

            SubentityType.Vertex);

 

        ed.WriteMessage("\n- Vertex Subentities: ");

 

        foreach (SubentityId subentId in vertexIds)

        {

            FullSubentityPath path = new FullSubentityPath(entId, subentId);

 

            DBPoint vertex = entity.GetSubentity(path) as DBPoint;

 

            if (vertex != null)

            {

                ed.WriteMessage(

                    "\n . Vertex: [{0}, {1}, {2}]",

                    vertex.Position.X,

                    vertex.Position.Y,

                    vertex.Position.Z);

 

                vertex.Dispose();

            }

        }

 

        SubentityId[] edgeIds = subentityIdPE.GetAllSubentities(

            entity,

            SubentityType.Edge);

 

        ed.WriteMessage("\n- Edge Subentities: ");

 

        foreach (SubentityId subentId in edgeIds)

        {

            FullSubentityPath path = new FullSubentityPath(entId, subentId);

 

            Entity edgeEntity = entity.GetSubentity(path);

 

            if (edgeEntity != null)

            {

                ed.WriteMessage("\n . " + edgeEntity.ToString());

                edgeEntity.Dispose();

            }

        }

 

 

        SubentityId[] faceIds = subentityIdPE.GetAllSubentities(

            entity,

            SubentityType.Face);

 

        ed.WriteMessage("\n- Face Subentities: ");

 

        foreach (SubentityId subentId in faceIds)

        {

            FullSubentityPath path = new FullSubentityPath(entId, subentId);

 

            Entity faceEntity = entity.GetSubentity(path);

 

            if (faceEntity != null)

            {

                ed.WriteMessage("\n . " + faceEntity.ToString());

                faceEntity.Dispose();

            }

        }

    }

}