Set the cursor that is displayed when hovering a View. (macOS, SwiftUI)

View+NSCursor.swift

import SwiftUI

extension View {
    /// https://stackoverflow.com/a/61985678/3393964
    public func cursor(_ cursor: NSCursor) -> some View {
        self.onHover { inside in
            if inside {
                cursor.push()
            } else {
                NSCursor.pop()
            }
        }
    }
}

Honestly can't believe Button doesn't do this by default.

For me, the correct cursor shows briefly but then disappears.

A year later I'm back here with code that works:

extension View {
  public func cursor(_ cursor: NSCursor) -> some View {
    if #available(macOS 13.0, *) {
      return self.onContinuousHover { phase in
        switch phase {
        case .active(let p):
          cursor.push()
        case .ended:
          NSCursor.pop()
        }
      }
    } else {
      return self.onHover { inside in
        if inside {
          cursor.push()
        } else {
          NSCursor.pop()
        }
      }
    }
  }
}

Nice! Thank you for updating here as I will fix this in my projects too :D @lucasfeijo

Like its name says, onContinuousHover calls its callback continuously, resulting in many cursor pushes and only a single pop at the end. The result is that when the cursor leaves the view, the original cursor is not restored. So here's my modification:

extension View {
    public func cursor(_ cursor: NSCursor) -> some View {
        if #available(macOS 13.0, *) {
            return self.onContinuousHover { phase in
                switch phase {
                case .active(_):
                    guard NSCursor.current != cursor else { return }
                    cursor.push()
                case .ended:
                    NSCursor.pop()
                }
            }
        } else {
            return self.onHover { inside in
                if inside {
                    cursor.push()
                } else {
                    NSCursor.pop()
                }
            }
        }
    }
}

@humblehacker We'll get it right eventually, meanwhile @apple has been ignoring this bug...