Topic: ssget and zoom level

[cuda]

hi,
I'm using this code: (ssget "C" Pt1 Pt2 '((0 . "MText"))) to select a Mtext. Normally it works properly and a Mtext entity is selected as I expect. The problem is when I zoom out my drawing to a very very small size, the selection set that it returns has more than one Mtext and these Mtexts are not even inside of the crossing box by (Pt1 Pt2). Apparently, the return of ssget function with "C" mode is influenced by zoom level.
Does anybody know how to solve this problem?

[Lee Mac]

hi,
I'm using this code: (ssget "C" Pt1 Pt2 '((0 . "MText"))) to select a Mtext. Normally it works properly and a Mtext entity is selected as I expect. The problem is when I zoom out my drawing to a very very small size, the selection set that it returns has more than one Mtext and these Mtexts are not even inside of the crossing box by (Pt1 Pt2). Apparently, the return of ssget function with "C" mode is influenced by zoom level.
Does anybody know how to solve this problem?

Yes, graphical selection methods (Window/Crossing/Polygon/Fence etc.) are influenced by the current zoom level; I recall that the term 'pixel flooding' has been previously used to describe the method used by AutoCAD to obtain a selection via these methods, which would explain why the zoom level is a factor in the result.

To avoid issues using these methods, I would suggest zooming the drawing to a window just slightly larger than your selection window, to provide the best opportunity to obtain an accurate selection.

[cuda]

Yes, graphical selection methods (Window/Crossing/Polygon/Fence etc.) are influenced by the current zoom level; I recall that the term 'pixel flooding' has been previously used to describe the method used by AutoCAD to obtain a selection via these methods, which would explain why the zoom level is a factor in the result.

To avoid issues using these methods, I would suggest zooming the drawing to a window just slightly larger than your selection window, to provide the best opportunity to obtain an accurate selection.

Thanks Lee, looks like there's no solution for this. I've changed the code to: (ssget "F" (list Pt1 Pt2) '((0 . "MText"))) and it works better than "C" mode or "W" mode.

[Crank]

Autodesk should solve this, but I'm afraid that will never happen.

If it's really important to you, you can make a work around for this bug:
Select all MTEXT and compare their bounding boxes with your (virtual) crossing to get the selection set.