- 3月9日补充,和评论区的大佬讨论了下,结合我的项目,彻底研究下该问题,其根本原因一句话概括,导航条返回手势和ScrollView手势有冲突,其实一共两个解决方案
- 1: 在特定的时候,干掉UIScrollView的手势,没有手势自然不存在冲突,我这篇文章介绍的是通过继承重写UIScrollView的函数在特定时候干掉自己的手势
- 2: 改变手势的依赖关系,或者说是手势的优先级关系,让nav的返回手势优先于ScrollView的手势,具体做法可以看下这位大佬的文章[UIScrollView与导航控制器滑动返回手势冲突问题原因与解决方案]
开发中,有部分UI,会将UIScrollView横向铺在底层,上面放tableView 或一些视图左右滚动切换,底层的scrollView会和Nav ViewController原有的返回手势冲突
解决办法,重写UIScrollView 的gestureRecognizerShouldBegin,在ScrollView滚动到头的时候,屏蔽ScrollView的手势
class GesturesConflictScrollView: UIScrollView {
override func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool {
back(by: gestureRecognizer)
}
private final func back(by gestureRecognizer: UIGestureRecognizer) -> Bool {
guard gestureRecognizer == panGestureRecognizer else { return true }
// point.x < 0 代表左滑即手指从屏幕右向左移动 反之一样
let point: CGPoint = panGestureRecognizer.translation(in: self)
let state: UIGestureRecognizer.State = gestureRecognizer.state
let locDistance: CGFloat = UIScreen.main.bounds.size.width
if state == .began || state == .possible {
let locationPoint = gestureRecognizer.location(in: self)
if point.x > 0 && locationPoint.x < locDistance && contentOffset.x <= 0 {
return false
}
let pageCount = contentSize.width / UIScreen.main.bounds.size.width
let criticalPoint = pageCount < 2 ? locDistance : locDistance * (pageCount - 1)
if point.x < 0 && contentOffset.x == criticalPoint {
return false
}
}
return true
}
}