I think the natural thing is organize it around one individual active touch. In touchesMoved, touchesEnded, and touchesCancelled, ignore everything when there's no active touch, and ignore any touches that are not the active touch. In touchesBegan, ignore new touches if there's already an active touch. Finally, in touchesBegan, if there's no active touch and the touch is on a ball, that touch becomes the active one and that ball becomes the being-moved ball. Sketch:
// activeTouch is a UITouch?
override func touchesBegan(_ touches: Set<UITouch>, with event: UIEvent?) {
for touch in touches {
if activeTouch == nil {
// Look for a touched ball; if found set that as the moving ball
// and set this touch as activeTouch
}
}
}
override func touchesMoved(_ touches: Set<UITouch>, with event: UIEvent?){
guard let active = activeTouch else { return }
for touch in touches {
if touch == active {
// Do stuff with the moving ball
}
}
}
override func touchesEnded(_ touches: Set<UITouch>, with event: UIEvent?){
guard let active = activeTouch else { return }
for touch in touches {
if touch == active {
// The moving ball stops moving, reset activeTouch to nil
}
}
}
// Probably touchesCancelled should be the same as touchesEnded, or
// maybe you'd want to move the ball back to the starting position;
// depends on your game.
I thought I WAS doing that. Thanks to your simplified template I found where I was messing up. Thank you