Arizona Posted February 7, 2017 Share Posted February 7, 2017 I use hatches to extract quantities of stuff like concrete, pavement, wetlands fill, etc. Most of the time, the hatch has an "area" embedded in it's code. When you select it, the Properties dialog box has a Geometry section at the bottom that lists it's area. The lisp routines I've written extract this area, convert to square yards, cubic yards, acres, tons of asphalt, or whatever you need, and do an appropriate thing with that info. Every once and a while, a hatch will Not have an area. When you select it, the properties dialog box does not have "area" in the Geometry section. In these cases, my lisp routines error out. When this happens I have to take the time to create a closed polyline around the area, then create a new hatch, using the closed pline. That usually does the trick. Does anyone understand why this happens? What am I doing wrong in the creation of the bad hatch? These hatches are all created exactly the same way, with the 'pick point' method, so why would it yield different results? Thanks for any light you can shed on this phenomenon. Quote Link to comment Share on other sites More sharing options...
rkent Posted February 7, 2017 Share Posted February 7, 2017 Maybe with HATCHEDIT you could use the recreate boundary option? Quote Link to comment Share on other sites More sharing options...
BIGAL Posted February 8, 2017 Share Posted February 8, 2017 Check out colour bylayer of the hatch I had some sort of problem. re error if arnew is nil. (SETQ ARNEW (vla-get-area (vlax-ename->vla-object en))) Quote Link to comment Share on other sites More sharing options...
Debalance Posted February 8, 2017 Share Posted February 8, 2017 ...What am I doing wrong in the creation of the bad hatch? These hatches are all created exactly the same way, with the 'pick point' method, so why would it yield different results? For alternative creating of hatchs or polylines you can try SuperBoundary utility instead standard BHATCH / BOUNDARY commands: You can download it via this link. Quote Link to comment Share on other sites More sharing options...
OMEGA-ThundeR Posted February 8, 2017 Share Posted February 8, 2017 I have a theory that this 'error' occurs when a hatch has arc in them. And to be precise, an overshooting arc As the below image shows. It is usually the case, so you could easely fix the error if you look as these arc spots. Quote Link to comment Share on other sites More sharing options...
Aftertouch Posted February 8, 2017 Share Posted February 8, 2017 @OMEGA-ThunderR Your sugestion is not a theory, its a fact. :-) An quick fix is to make a new boundary of the hatch, and then hatch that boundary again. :-) Will fix the problem most of the times. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.