Gesture handling in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to detect a tap gesture on a View.

Android Kotlin

val gestureDetector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {
    override fun onSingleTapUp(e: MotionEvent?): Boolean {
        Toast.makeText(this@MainActivity, "Tapped!", Toast.LENGTH_SHORT).show()
        return [1]
    }
})

Drag options to blanks, or click blank then click option'

AUnit

Bfalse

Cnull

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Returning false causes the tap event to be ignored.

Returning null or Unit causes a compile error.

Returning true means the tap event was handled successfully.

2fill in blank

medium

Complete the code to set a touch listener that passes events to the gesture detector.

Android Kotlin

myView.setOnTouchListener { v, event ->
    [1].onTouchEvent(event)
}

Drag options to blanks, or click blank then click option'

AgestureDetector

Bthis

Cv

Devent

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'this' instead of gestureDetector causes errors.

Using 'v' or 'event' does not call the gesture detector.

The gestureDetector handles the touch events to detect gestures.

3fill in blank

hard

Fix the error in the gesture listener to detect a long press gesture.

Android Kotlin

val gestureListener = object : GestureDetector.SimpleOnGestureListener() {
    override fun onLongPress(e: MotionEvent?) {
        super.[1](e)
        Toast.makeText(context, "Long pressed", Toast.LENGTH_SHORT).show()
    }
}

Drag options to blanks, or click blank then click option'

AonSingleTapUp

BonLongPress

ConDoubleTap

DonScroll

Attempts:

3 left

💡 Hint

Common Mistakes

Calling super.onSingleTapUp causes the long press not to work.

Omitting the super call can cause unexpected behavior.

Calling super.onLongPress ensures the base class handles the long press event properly.

4fill in blank

hard

Fill both blanks to detect a fling gesture with velocity check.

Android Kotlin

override fun onFling(e1: MotionEvent?, e2: MotionEvent?, velocityX: Float, velocityY: Float): Boolean {
    if (velocityX > [1] && velocityY > [2]) {
        Toast.makeText(context, "Fling detected", Toast.LENGTH_SHORT).show()
        return true
    }
    return false
}

Drag options to blanks, or click blank then click option'

A1000f

B500f

C1500f

D200f

Attempts:

3 left

💡 Hint

Common Mistakes

Using too low velocity values causes false positives.

Using integers instead of floats causes type errors.

Velocity thresholds like 1000f and 500f help detect a fast enough fling gesture.

5fill in blank

hard

Fill all three blanks to create a gesture detector that recognizes double taps and single taps.

Android Kotlin

val gestureDetector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {
    override fun onDoubleTap(e: MotionEvent?): Boolean {
        Toast.makeText(context, "Double tap", Toast.LENGTH_SHORT).show()
        return [1]
    }

    override fun onSingleTapConfirmed(e: MotionEvent?): Boolean {
        Toast.makeText(context, "Single tap", Toast.LENGTH_SHORT).show()
        return [2]
    }

    override fun onDown(e: MotionEvent?): Boolean {
        return [3]
    }
})

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

Csuper.onDown(e)

DUnit

Attempts:

3 left

💡 Hint

Common Mistakes

Returning false in tap handlers causes gestures to be ignored.

Returning Unit causes compile errors.

Not calling super.onDown causes gesture detection issues.

Return true in onDoubleTap and onSingleTapConfirmed to indicate event handled; onDown should call super.onDown.

Practice

1. What is the primary purpose of using GestureDetector in Android Kotlin apps?

easy

A. To detect user gestures like taps and swipes on a view

B. To create animations for UI components

C. To manage app navigation between screens

D. To handle database operations asynchronously

Solution

1. Step 1: Understand GestureDetector role

   GestureDetector is designed to listen for user touch gestures such as taps, swipes, and long presses on views.

2. Step 2: Compare other options

   Options A, B, and D relate to navigation, animations, and database tasks, which are unrelated to gesture detection.

3. Final Answer:

   To detect user gestures like taps and swipes on a view -> Option A

4. Quick Check:

   GestureDetector = Detect gestures [OK]

Hint: GestureDetector listens for touch gestures on views [OK]

Common Mistakes:

• Confusing GestureDetector with animation tools
• Thinking GestureDetector manages navigation
• Assuming GestureDetector handles data tasks

2. Which of the following is the correct way to create a GestureDetector with a simple gesture listener in Kotlin?

easy

A. val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {})

B. val detector = GestureDetector(object : GestureDetector.SimpleOnGestureListener() {}, this)

C. val detector = GestureDetector(this, GestureListener())

D. val detector = GestureDetector.SimpleOnGestureListener(this)

Solution

1. Step 1: Check GestureDetector constructor syntax

   The constructor takes a Context (usually 'this') and a GestureDetector.OnGestureListener implementation, often an anonymous object of SimpleOnGestureListener.

2. Step 2: Validate options

   val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {}) matches the correct syntax. val detector = GestureDetector(object : GestureDetector.SimpleOnGestureListener() {}, this) reverses parameters. val detector = GestureDetector(this, GestureListener()) uses an undefined class. val detector = GestureDetector.SimpleOnGestureListener(this) incorrectly calls SimpleOnGestureListener as a constructor.

3. Final Answer:

   val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {}) -> Option A

4. Quick Check:

   Context first, listener second in GestureDetector constructor [OK]

Hint: Context is first, listener second in GestureDetector constructor [OK]

Common Mistakes:

• Swapping constructor parameters order
• Using undefined listener classes
• Calling listener as a constructor

3. Given this Kotlin code snippet inside an Activity:

val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {
  override fun onSingleTapUp(e: MotionEvent?): Boolean {
    println("Tapped")
    return true
  }
})

view.setOnTouchListener { _, event ->
  detector.onTouchEvent(event)
  true
}

What will happen when the user taps on the view?

medium

A. The view ignores the tap and does not respond

B. Nothing happens because onSingleTapUp is not called

C. The message "Tapped" is printed to the console

D. The app crashes due to missing return statement

Solution

1. Step 1: Understand onSingleTapUp override

   The overridden method prints "Tapped" and returns true, indicating the tap gesture was handled.

2. Step 2: Check touch listener behavior

   The touch listener passes events to the detector, which triggers onSingleTapUp on tap, so "Tapped" is printed.

3. Final Answer:

   The message "Tapped" is printed to the console -> Option C

4. Quick Check:

   onSingleTapUp triggers print on tap [OK]

Hint: onSingleTapUp prints message when tap detected [OK]

Common Mistakes:

• Assuming onSingleTapUp is never called
• Forgetting to return true to handle gesture
• Ignoring event forwarding to GestureDetector

4. What is wrong with this Kotlin code snippet for gesture detection?

val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {
  override fun onLongPress(e: MotionEvent?) {
    println("Long press detected")
  }
})

view.setOnTouchListener { _, event ->
  detector.onTouchEvent(event)
}

medium

A. MotionEvent parameter cannot be nullable

B. onLongPress must return a Boolean

C. GestureDetector requires a separate listener for long press

D. The onTouchListener does not return a Boolean value

Solution

1. Step 1: Check onTouchListener return type

   onTouchListener must return a Boolean indicating if the event was handled. This code lacks a return statement.

2. Step 2: Validate other parts

   onLongPress returns void (Unit) correctly. GestureDetector supports long press in the same listener. MotionEvent can be nullable.

3. Final Answer:

   The onTouchListener does not return a Boolean value -> Option D

4. Quick Check:

   onTouchListener must return Boolean [OK]

Hint: Always return Boolean from onTouchListener [OK]

Common Mistakes:

• Forgetting to return true or false in onTouchListener
• Expecting onLongPress to return Boolean
• Misunderstanding nullable MotionEvent

5. You want to detect both single taps and double taps on a view using GestureDetector in Kotlin. Which approach correctly handles both gestures without conflict?

hard

A. Use two separate GestureDetectors, one for single tap and one for double tap, attached to the same view

B. Use GestureDetector with a GestureDetector.OnDoubleTapListener and override both onSingleTapConfirmed and onDoubleTap methods

C. Override only onSingleTapUp and ignore double taps to avoid conflicts

D. Use onTouchListener to manually count taps and ignore GestureDetector

Solution

1. Step 1: Understand GestureDetector double tap support

   GestureDetector supports double tap detection via OnDoubleTapListener interface, which includes onSingleTapConfirmed and onDoubleTap methods.

2. Step 2: Evaluate options for handling both taps

   Use GestureDetector with a GestureDetector.OnDoubleTapListener and override both onSingleTapConfirmed and onDoubleTap methods correctly uses OnDoubleTapListener to distinguish single and double taps. Use two separate GestureDetectors, one for single tap and one for double tap, attached to the same view causes conflicts with multiple detectors. Override only onSingleTapUp and ignore double taps to avoid conflicts ignores double taps. Use onTouchListener to manually count taps and ignore GestureDetector is manual and error-prone.

3. Final Answer:

   Use GestureDetector with a GestureDetector.OnDoubleTapListener and override both onSingleTapConfirmed and onDoubleTap methods -> Option B

4. Quick Check:

   OnDoubleTapListener handles single and double taps [OK]

Hint: Use OnDoubleTapListener to handle single and double taps [OK]

Common Mistakes:

• Using multiple GestureDetectors on one view
• Ignoring double tap detection
• Manually counting taps instead of using listener