Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.
Rust agentai-agentapplecomputer-usecomputer-use-agentcontainerizationcuadesktop-automationhacktoberfestlumemacosmanusoperatorswiftvirtualizationvirtualization-frameworkwindowswindows-sandbox
fix(cua-driver): remove zero-caller macOS drag and AXValue helpers (#5962)
injaneity07c121eed04e
diff --git a/libs/cua-driver/rust/crates/platform-macos/src/input/ax_actions.rs b/libs/cua-driver/rust/crates/platform-macos/src/input/ax_actions.rsindex 0adce0e332..e086e51e14 100644--- a/libs/cua-driver/rust/crates/platform-macos/src/input/ax_actions.rs+++ b/libs/cua-driver/rust/crates/platform-macos/src/input/ax_actions.rs@@ -296,16 +296,6 @@ pub fn element_has_keyboard_focus(pid: i32, element_ptr: usize) -> bool {|| unsafe { copy_bool_attr(element_ptr as AXUIElementRef, "AXFocused") } == Some(true)}-/// Set the AXValue of an element (for dropdowns, text fields, etc.).-pub fn set_ax_value(element_ptr: usize, value: &str) -> anyhow::Result<()> {- let err = unsafe { set_string_attr(element_ptr as AXUIElementRef, "AXValue", value) };- if err == kAXErrorSuccess {- Ok(())- } else {- anyhow::bail!("AXUIElementSetAttributeValue(AXValue) failed with error {err}")- }-}-#[cfg(test)]mod tests {#[test]diff --git a/libs/cua-driver/rust/crates/platform-macos/src/input/mouse.rs b/libs/cua-driver/rust/crates/platform-macos/src/input/mouse.rsindex 1b34151cb8..9ec6e1096c 100644--- a/libs/cua-driver/rust/crates/platform-macos/src/input/mouse.rs+++ b/libs/cua-driver/rust/crates/platform-macos/src/input/mouse.rs@@ -739,50 +739,6 @@ pub fn click_at_xy_chromium(Ok(())}-/// Press-drag-release gesture from `(from_x, from_y)` to `(to_x, to_y)` in-/// screen coordinates, addressed to `pid` and the optional exact window.-///-/// `duration_ms` is the wall-clock budget for the drag path; `steps` is the-/// number of intermediate `leftMouseDragged` events linearly interpolated-/// along the path. `modifiers` are held across the entire gesture.-///-/// Like the Swift reference `MouseInput.drag`, uses the SkyLight path for-/// backgrounded-target delivery.-// The drag primitive deliberately exposes its complete native event contract.-#[allow(clippy::too_many_arguments)]-pub fn drag_at_xy(- pid: i32,- from_x: f64,- from_y: f64,- to_x: f64,- to_y: f64,- from_local: Option<(f64, f64)>,- to_local: Option<(f64, f64)>,- wid: Option<u32>,- duration_ms: u64,- steps: usize,- modifiers: &[&str],- button: DragButton,- foreground_hid: bool,-) -> anyhow::Result<()> {- drag_at_xy_observed(- pid,- from_x,- from_y,- to_x,- to_y,- from_local,- to_local,- wid,- duration_ms,- steps,- modifiers,- button,- foreground_hid,- |_, _| {},- )-}-/// Window drag with an observer called for every native pointer position.////// Background delivery keeps the established PID-routed sequence. When@@ -1224,37 +1180,6 @@ whereOk(())}-/// Foreground drag through the global HID event tap.-///-/// A frontmost Chromium/WebKit surface expects a real HID-origin gesture for-/// pointer capture and drag tracking. PID-routed `post_to_pid` events are-/// suitable for background delivery, but they can be silently filtered by the-/// renderer even when the target is frontmost.-// The drag primitive deliberately exposes its complete native event contract.-#[allow(clippy::too_many_arguments)]-pub fn drag_at_xy_foreground(- from_x: f64,- from_y: f64,- to_x: f64,- to_y: f64,- duration_ms: u64,- steps: usize,- modifiers: &[&str],- button: DragButton,-) -> anyhow::Result<()> {- drag_at_xy_foreground_observed(- from_x,- from_y,- to_x,- to_y,- duration_ms,- steps,- modifiers,- button,- |_, _| {},- )-}-/// Foreground drag with an observer called for every native pointer position.////// The cursor overlay uses this to follow the same interpolated path and