gpui: Add "swipe to navigate" for macOS

[seivan]

Closes #4954

Replaces #14939

Release Notes:

Added:

• Swipe to Navigate for macOS
• Listeners for both horizontal and vertical swipes
• Only active for horizontal for now

Requires these macOS settings:

Older macOS settings:

Note:
I altered the logic from #23332 or more specifically, I hard-coded the values to match native macOS swiping. I don't have that exact mouse and software to try to see if it works with the new values.
Either way, mouse navigation with btn4/5 still works out of the box on macOS for most mouses.
Whatever custom software that mouse uses, it disguises itself as a swipe event, so hopefully it also matches the delta values of one.

Thinking of using config to register custom actions to send for either axis, while defaulting for tab navigation for horizontal, and disabled for vertical, but that would be a separate PR.

Something like

"workbench.editor.swipeToNavigate": {
  "horizontal": "disabled",
  "vertical": { "previous": "customAction", "next": "someOtherCustomAction" }
}

Release Notes:

• Added three finger swipe to navigate.

[Copilot]

Pull Request Overview

Implements swipe gesture navigation for macOS, allowing users to navigate tabs using horizontal swipe gestures on trackpads. This feature maps left swipe to "pane::GoBack" and right swipe to "pane::GoForward" actions.

• Adds touchpad gesture support infrastructure with TouchPadGestureEvent and SwipeDirection types
• Converts macOS swipe events from mouse navigation simulation to proper touchpad gesture events
• Implements swipe-to-action mapping in the window event dispatcher

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
crates/gpui/src/interactive.rs	Adds touchpad gesture event types and platform input handling
crates/gpui/src/platform/mac/events.rs	Converts macOS swipe events to touchpad gestures instead of mouse navigation
crates/gpui/src/window.rs	Implements swipe gesture event dispatching and action mapping

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[seivan]

Warnings
⚠️
This PR is missing release notes.

Please add a "Release Notes" section that describes the change:

Release Notes:

- Added/Fixed/Improved ...

If your change is not user-facing, you can use "N/A" for the entry:

Release Notes:

- N/A

Generated by 🚫 dangerJS against 7eafc45

Done

[seivan]

Fixed formatting issues with imports.

[seivan]

@ConradIrwin Any chance you can take a look at this now? It's been more than six weeks now.

[mikayla-maki]

Hello!

Please add or modify a GPUI example to demonstrate this touch behavior, so that we can test this :)

[seivan]

Hello!

Please add or modify a GPUI example to demonstrate this touch behavior, so that we can test this :)

Hello!

Please add or modify a GPUI example to demonstrate this touch behavior, so that we can test this :)

I'm a bit confused here, are you saying you're currently unable to test it as is?
Or that you really want a separate demo example in crates/gpui/examples?

[mikayla-maki]

Or that you really want a separate demo example in crates/gpui/examples?

✅ separate examples make it easy to test how features look and feel, and are the primary way they're developed and documented in GPUI right now. See the window_positioning example, for example! :D

[seivan]

Or that you really want a separate demo example in crates/gpui/examples?

✅ separate examples make it easy to test how features look and feel, and are the primary way they're developed and documented in GPUI right now. See the window_positioning example, for example! :D

Yeah but this is a feature for Zed, not the gpui crate.

I would have to put a large portion of Zed, more specifically crates/workspace/src as an example as it requires Panes to be demoed. You guys added the gpui tag here, not me. If you are ok with that, then sure.

[seivan]

Actually, I think I got it. One sec.