topic Re: AcdbHatch::getLoopAt Problem ... in ObjectARX Forum

AcdbHatch::getLoopAt Problem ...

Anonymous — Mon, 26 Mar 2018 12:11:27 GMT

try to get hatch boundry vertex by using " getLoopAt " method but Autocad shows some "Assertion Failed" error..

Code::

AcDbHatch* aHac = AcDbHatch::cast(aEnt);

if (aHac->loopTypeAt(ind) & AcDbHatch::kPolyline)
{

Adesk::Int32 loopType;

AcGePoint2dArray vertices;
AcGeDoubleArray bulges;

aHac->getLoopAt(ind,loopType,vertices,bulges);
int nver = vertices.length();
acutPrintf(_T("\n%d"),nver);
}

Re: AcdbHatch::getLoopAt Problem ...

Alexander.Rivilis — Mon, 26 Mar 2018 12:17:00 GMT

It is look like value of ind is not setting before aHac->loopTypeAt(ind) calling.

Re: AcdbHatch::getLoopAt Problem ...

Anonymous — Mon, 26 Mar 2018 12:26:35 GMT

thanks for replay..but i have already given "ind (index) " value ...

int numVer = aHac->numLoops();
acutPrintf(_T("\n%d"), numVer);
for (int ind = 0; ind < numVer; ind++)
{
//acutPrintf(_T("\npolyline"));

if (aHac->loopTypeAt(ind) & AcDbHatch::kPolyline)
{

int32_t loopType;

AcGePoint2dArray vertices;
AcGeDoubleArray bulges;

aHac->getLoopAt(ind,loopType,vertices,bulges);
int nver = vertices.length();
acutPrintf(_T("\n%d"),nver);
}
}

Re: AcdbHatch::getLoopAt Problem ...

Alexander.Rivilis — Mon, 26 Mar 2018 12:40:14 GMT

1. AutoCAD version?

2. Visual Studio version and updates?

Re: AcdbHatch::getLoopAt Problem ...

Anonymous — Mon, 26 Mar 2018 12:42:24 GMT

Autocad 2018

Visual Studio 2015..

Re: AcdbHatch::getLoopAt Problem ...

Alexander.Rivilis — Mon, 26 Mar 2018 12:45:50 GMT

@Anonymous написал (-а):

Autocad 2018

Visual Studio 2015..

Visual Studio 2015 or Visual Studio 2015 with Update 3 ???

P.S.: Try this sample code: http://adndevblog.typepad.com/autocad/2012/04/perimeter-of-a-hatch-using-objectarx-and-autocad-net-api.html

Re: AcdbHatch::getLoopAt Problem ...

Anonymous — Mon, 26 Mar 2018 12:49:13 GMT

thanks Sir ...i already see this example ...

is their any other method to get the vertices of the Hatch..(Polyline)..

Re: AcdbHatch::getLoopAt Problem ...

Anonymous — Wed, 28 Mar 2018 13:43:02 GMT

code::

if (aHac->loopTypeAt(ind) & AcDbHatch::kExternal)
{
acutPrintf(_T("\nexternal hatch"));

AcGeVoidPointerArray vert;
vert.setPhysicalLength(50);

AcGeIntArray bulges;

Adesk::Int32 loopType;

aHac->getLoopAt(ind,loopType, vert, bulges);
acutPrintf(_T("\n%d"), vert.length());

for (int i=0;i<vert.length()+1;i++)
{
if (i == vert.length())
{
break;
}

}

}

i'll try to get the "Acdb::kexternal" Hatch vertices ...but autocad get crash ...

please help..

Re: AcdbHatch::getLoopAt Problem ...

Alexander.Rivilis — Wed, 28 Mar 2018 17:05:26 GMT

@Anonymous

If you expect help, then attach an example of the ObjectARX project (in zip) and an example of a dwg-file for testing.

Re: AcdbHatch::getLoopAt Problem ...

Anonymous — Fri, 30 Mar 2018 12:04:55 GMT

code and dwg file

Re: AcdbHatch::getLoopAt Problem ...

Alexander.Rivilis — Fri, 30 Mar 2018 14:58:41 GMT

@Anonymous написал (-а):

code and dwg file

This is not what I asked for.

Re: AcdbHatch::getLoopAt Problem ...

autodaug — Sun, 01 Apr 2018 20:46:41 GMT

The assert message appears to be coming from MSVC's debug lib and is saying there's a heap corruption. There may be a mismatch between the app's c-runtime lib and acad'. E.g., if one is the debug lib and the other is the release lib, or maybe they are from different MSVC versions. The heap corruption can happen when memory is allocated from one runtime heap and then deleted onto another heap.

To work around this, you might try "pre-allocating" your arrays' buffers before calling the API. That way, acad will not need to grow your array, and so all allocation and de-allocation of your array buffers will be happening on your app's heap and none on acad's. E.g.:

AcGePoint2dArray vertices;
vertices.setPhysicalLength(1000);    // pre-allocate array so acad won't grow it
AcGeDoubleArray bulges;
bulges.setPhysicalLength(1000);     // use a size guaranteed to be big enuff

aHac->getLoopAt(ind,loopType,vertices,bulges);
assert(vertices.length() < 1000);      // make sure we're pre-allocating enough

This is kind of kludgy, but it's worth a try. If you google around for setPhysicalLength(), you can find other discussions of this workaround. However, if there is a runtime heap mismatch going on, then I would think you may run into stability problems in other areas too..