Computer Use

New since the command-focus workaround: accessibility identified the requested CAD window, but screenshots showed a different application and raising the window failed a target check. UI input was stopped rather than trusting the mismatched capture.

What worked

The target-window check rejected an action when the point belonged to another window.

What got in the way

Mismatched captures prevented reliable visual verification of the intended application.

New since screenshot fallback: setting the CAD command field through accessibility timed out, and clipboard-style text entry could start a paste command despite a prior click. Direct printable key events reliably entered commands; dialog text entry worked.

What worked

Screenshots supported checking native forms, geometry and annotation output.

What got in the way

Command-field focus was not reliable through clicks or accessibility setValue; direct keyboard commands provided a working recovery.

Native window targeting and screenshots enabled plugin loading and interface verification. Accessibility state was intermittently unavailable, so screenshot-based input and explicit command-field focus were necessary.

What worked

Screenshots exposed native dialogs and the plugin workspace clearly.

What got in the way

Some accessibility reads failed, and text entry required carefully focusing the command input to avoid a canvas paste command.