| < How to force one gesture to recognize before another using highPriorityGesture() | How to create gesture chains using sequenced(before:) > |
How to make two gestures recognize at the same time using simultaneousGesture()
Updated for Xcode 14.0 beta 1
By default SwiftUI will trigger only one gesture recognizer action at a time, which is usually whichever one is the front-most view in your hierarchy – it would prefer a recognizer on a child view rather than its parent, for example. If you want to override this behavior to make two gestures trigger at once, you should use the simultaneousGesture() when creating your second and subsequent gestures.
For example, in this code we have two tap gestures, but SwiftUI will execute only the one attached to the circle because it’s the child of the VStack:
struct ContentView: View {
var body: some View {
VStack {
Circle()
.fill(.red)
.frame(width: 200, height: 200)
.onTapGesture {
print("Circle tapped")
}
}
.onTapGesture {
print("VStack tapped")
}
}
}
Download this as an Xcode project
If you want both gestures to trigger – i.e., if you want both “Circle tapped” and “VStack tapped” to be printed – you should use simultaneousGesture() on the VStack like this:
struct ContentView: View {
var body: some View {
VStack {
Circle()
.fill(.red)
.frame(width: 200, height: 200)
.onTapGesture {
print("Circle tapped")
}
}
.simultaneousGesture(
TapGesture()
.onEnded { _ in
print("VStack tapped")
}
)
}
} Download this as an Xcode project
Note: You should use simultaneousGesture() with the gesture that would otherwise not be executed otherwise it won’t work. So, in our previous example using simultaneousGesture() with the circle and a simple onTapGesture() with the VStack will still print just “Circle tapped” – it won’t do what you expect.
SPONSORED You know StoreKit, but you don’t want to do StoreKit. RevenueCat makes it easy to deploy, manage, and analyze in-app subscriptions on iOS and Android so you can focus on building your app.
Sponsor Hacking with Swift and reach the world's largest Swift community!
Similar solutions…
