AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() In the particular configuration of the sample drawing, its location calculation lands right on the diagonal edge Lines halfway between their intersections with the horizontal/vertical Lines, so the Boundary command gets a message to that effect for all those locations, and it does not put Regions into any of those triangular spaces. And it runs faster, because it doesn't ever pick more than once within the same area. That suggests that my guess was correct about the previous version having its pick locations sometimes misread in relation to Line positions when they're really close together at the current Zoom level. So I tried that approach, which actually takes less code, and it seems to catch all the locations even within the closely-spaced Lines and Zoomed out far enough to see the whole grid. It could also be done by actually finding one location within each space in the grid, with a different kind of calculation for the pick points. That could probably be avoided by making the step spacing equal in both directions, based on the smallest Line spacing in either direction, but that would make it take that much longer to wrote: When it catches the rectanglular space just below one of those triangles by picking near enough to the top of it, and close enough horizontally to the diagonal edge Line, the next pick upward from there that can easily be above the diagonal edge, so that triangle will be missed if the horizontal stepping takes it past the vertical side of the triangle. I suspect it will always miss at least some of the triangular areas along the sloped edges, because of the way it steps vertically. ![]() And it certainly speeds it up to do the central area, with the vertical Lines spaced farther apart, separately from the side areas, because it can use so much greater a stepping distance in the horizontal direction. It could be that Zooming in and doing it in smaller areas may overcome that. I get fewer Regions when I run it in Plan view than in the non-Plan view as the drawing was posted, probably because I can't zoom in quite as closely around the whole grid. I suspect the missing Regions are probably a result of the closeness of the vertical Line spacing in the triangular side areas, and the limitations on its "reading" the position of point selections when zoomed out enough to see the whole grid. I have tested ONLY with the upper left figure ! about 218 lines. [Also, it doesn't yet have various things that ought to be added - error handling, Undo begin/end, command-echo suppression, blipmode suppression if appropriate, wrote:Ģnd Run : very fast about 3 mns !!! -> 1938 Regionsīut the DWG was in the Top View. And it even seems to miss some of the internal rectangular ones in the areas of very-closely-spaced vertical Lines , but that may possibly be affected by Zoom level. In the angled-sides configuration in their sample drawing, it won't necessarily catch all the triangular areas along the sloped edges. The attached upgraded version accounts for that. It turned out there are a few Lines in the grids that coincide or overlap, which means one and/or the other stepping increment gets set to zero, so it never got anywhere. Thank you! But when I tried it on the OP's sample drawing, it got stuck. Tool Bar Lisp Routine Adjustment Help 1. ![]()
0 Comments
Read More
Leave a Reply. |