Handle multiple mouse event types in common.rs

[sje397]

Without this fix, mouse movements during drag on osx aren't reported.

[rustdesk]

@fufesou

[Copilot]

Pull request overview

This PR fixes an issue where mouse movements during drag operations on macOS weren't being reported. The fix extends the pattern matching in the event conversion logic to handle drag events as mouse movement events.

Key changes:

• Extended pattern matching to treat LeftMouseDragged, RightMouseDragged, and OtherMouseDragged events as MouseMove events

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The new behavior of treating drag events as mouse move events lacks test coverage. Consider adding tests that verify LeftMouseDragged, RightMouseDragged, and OtherMouseDragged events are correctly converted to EventType::MouseMove, similar to the existing MouseMove tests in tests/listen_and_simulate.rs.

[Copilot]

The event mask kCGEventMaskForAllEvents is missing OtherMouseDragged. While this line correctly handles OtherMouseDragged events in the conversion logic, these events will never be received because they're not registered in the event mask. Add + (1 << CGEventType::OtherMouseDragged as u64) after line 71 in the event mask definition to ensure these events are captured.

[fufesou]

I can verify that CGEventType::LeftMouseDragged and CGEventType::RightMouseDragged work.

The event mask kCGEventMaskForAllEvents is missing OtherMouseDragged. While this line correctly handles OtherMouseDragged events in the conversion logic, these events will never be received because they're not registered in the event mask. Add + (1 << CGEventType::OtherMouseDragged as u64) after line 71 in the event mask definition to ensure these events are captured.

This suggestion may make sense.

My mouse does not produce CGEventType::OtherMouseDragged events by default. Adding + (1 << CGEventType::OtherMouseDragged as u64) enables listening for middle‑button drags as that event type.

This is a minor point. In any case, the PR LGTM.

By the way, RustDesk does not capture mouse events via rdev; it uses Flutter's built-in functions for that.