使用Editor.SelectCrossingWindow选实体报错，示例代码无效但SelectAll正常

I see you're stuck with an issue where Editor.SelectCrossingWindow keeps returning an error status—even when using sample code from Autodesk's docs—while ed.SelectAll works perfectly fine. Let's break down the most likely causes and fixes to get this sorted:

Common Causes & Solutions #

• Coordinate System Mismatch
  The top culprit here is usually a mismatch between the coordinate system you're using and the editor's active space. SelectCrossingWindow relies on coordinates relative to the current editor's active viewport (model space vs. paper space).

  • Fix: Explicitly switch to the correct space before calling the method, or transform your points to match the editor's current UCS. Here's an adjusted code snippet:

    // Switch to model space first if needed
    if (acDocEd.CurrentSpace != Space.ModelSpace)
    {
        acDocEd.SwitchToModelSpace();
    }
    
    PromptSelectionResult acSSPrompt;
    acSSPrompt = acDocEd.SelectCrossingWindow(new Point3d(2, 2, 0), new Point3d(10, 8, 0));
    if (acSSPrompt.Status == PromptStatus.OK) {
        SelectionSet acSSet = acSSPrompt.Value;
        Application.ShowAlertDialog("Number of objects selected: " + acSSet.Count.ToString());
    }
    

• No Entities Qualify for Selection
  Even if you think entities are in the target window, double-check these edge cases:

  • Are the entities on a locked layer? Locked layers block selection via window commands.
  • Do the entities exist on a different Z-plane? If your 3D points don't match the entities' elevation, the crossing window won't pick them up (try matching the Z-value or using Point2d for 2D workflows).
  • Are the entities outside the current viewport's extents? Zooming way out can make it look like entities are in the window when they're actually outside.

• Editor is in an Active Command State
  If AutoCAD is mid-command (like drawing a line or editing a block), selection methods like SelectCrossingWindow will fail.

  • Fix: Add a check to ensure no command is running before your selection code:

    if (acDoc.IsCommandActive())
    {
        Application.ShowAlertDialog("Please finish the active command first.");
        return;
    }
    

• Missing Transaction Context
  While SelectAll might work without an explicit transaction in some contexts, SelectCrossingWindow can be stricter about running within a valid transaction scope.

  • Fix: Wrap your code in a transaction:

    using (Transaction acTrans = acDoc.TransactionManager.StartTransaction())
    {
        PromptSelectionResult acSSPrompt = acDocEd.SelectCrossingWindow(new Point3d(2, 2, 0), new Point3d(10, 8, 0));
        if (acSSPrompt.Status == PromptStatus.OK)
        {
            SelectionSet acSSet = acSSPrompt.Value;
            Application.ShowAlertDialog("Number of objects selected: " + acSSet.Count.ToString());
        }
        acTrans.Commit();
    }
    

Quick Debug Trick #

Add a message to show the exact error status—it'll help you narrow down the issue faster:

if (acSSPrompt.Status != PromptStatus.OK)
{
    Application.ShowAlertDialog("Selection failed with status: " + acSSPrompt.Status.ToString());
}

This will tell you if it's PromptStatus.Error, PromptStatus.Cancel, or another specific status, guiding your troubleshooting.

内容的提问来源于stack exchange，提问作者Meh yit