Split up OnTouchListener

[romtsn]

Would it make sense to have something like

inline fun View.doOnActionUp(crossinline action: (event: MotionEvent) -> Unit)
inline fun View.doOnActionMove(crossinline action: (event: MotionEvent) -> Unit)
inline fun View.doOnActionCancel(crossinline action: (event: MotionEvent) -> Unit)
...

instead of wall of code in a single OnTouchListener ?

[JakeWharton]

We need to figure out a general multi-callback listener strategy... I'm going to coalesce these into a mega issue.

[dovahkiin98]

maybe something like this

view.onTouchListener (
    onActionUp = {

    },
    onActionDown = {

    }
)

[Edward608]

I think the similar to what @dovahkiin98 suggest, the same can be done to OnGestureListener

[xiaofeidev]

@dovahkiin98 I like this,this‘ s named DSL

[guxiaonian]

I just do this：
fun View.doOnTouchListener(
onTouch: Boolean,
onActionUp: ((motionEvent: MotionEvent) -> Unit)? = null,
onActionDown: ((motionEvent: MotionEvent) -> Unit)? = null,
onActionMove: ((motionEvent: MotionEvent) -> Unit)? = null
): View.OnTouchListener {
val listener = View.OnTouchListener { _, p1 ->
when (p1!!.action) {
MotionEvent.ACTION_UP -> onActionUp?.invoke(p1)
MotionEvent.ACTION_DOWN -> onActionDown?.invoke(p1)
MotionEvent.ACTION_MOVE -> onActionMove?.invoke(p1)
}
onTouch
}
setOnTouchListener(listener)
return listener
}

also：
tv.doOnTouchListener(true,
onActionDown = {
},
onActionMove = {
},
onActionUp = {
}
)