OK, I test it with VBA code. The result is the same: if you zoomed in to
certain degree (i.e. the selecting polygon is partly outside of current
view), Acad will not find entities inside th selecting polygon. But you
never know exactly when or zooed in how much the SelectByPolyGon (in VBA) or
SelectCrossingPolygon() (in .NET API) will fail. To garantee your code to
work, you have to make sure the polygon is ENTIRELY within the current view.
I probably have to admit that it is "BY DESIGN", although, if you manuall
issue commad "SELECT->CPolygon" and before your last pick of the polygon's
point, you zoom in very much so that the large part of the selecting polygon
is outside of current view, you still get CORRECT result, as you expected!
So, the "BY DESIGN" trick is really designed to fool programmers, who have
no way to know this "By Design" shortcomming until they were trapped in it
and struggled with their code debugging.
wrote in message news:5362272@discussion.autodesk.com...
It is by design. The same issue in VisualLisp/VBA/ObjectARX.