Hatch has no AREA??

[chulse]

How can it be that a hatch object has no area property?

 

Using the AREA command, it says the object has no area.

None shown in properties.

None listed using vlisp (vla-get-Area Obj).

 

I have seen this before, but could never figure out why or how it happens.

 

 

 

Any thoughts?

[rkmcswain]

Does the hatch boundary self intersect?

IIRC - this will cause the area property to be null.

[chulse]

Not sure about self-intersecting. Here it is.

bad_hatch.dwgFetching info...

[Tyke]

There's a loop in the outer boundary halfway down the right hand side. If you move your hatch and the cyan line crossing the road and then get rid of the loop in the boundary you can create the hatch again and it does have an area this time. I'm not sure if it was the loop or the cyan line that was causing the problem.

[chulse]

well I'll be...

 

so there's no way to force something like this, just fix it manually?

[Tyke]

rkmcswain gave the clue and I just followed it up. I didn't know about the problem caused when the boundary intersects itself, thanks for that rkms

[rkmcswain]

  Tyke said:

rkmcswain gave the clue and I just followed it up. I didn't know about the problem caused when the boundary intersects itself, thanks for that rkms

 

 

I think I ran across that one time - something like this:

 

 

That could be two separate hatches, or in this case a single object was selected, which is the polyline that crosses itself. An exaggerated example of course....

[chulse]

Thanks guys, makes sense now.

aside from fixing this sort of thing manually, there is no way to resolve it (programmatically I mean)?